Onboard Electronic Distribution System

ABSTRACT

A computer implemented method, apparatus, and computer program product for transferring information with an aircraft. A connection is established between an onboard electronic distribution system executing in an aircraft data processing system in the aircraft and an on ground component. Responsive to a request for a command from the on ground component, the command for execution is identified. The identified command is sent to the onboard electronic distribution system from an on ground component. A transaction identifier is assigned to the command. A transaction associated with the command is maintained on the onboard electronic distribution system and the on ground component using the transaction identifier. An uplink is initiated by the on ground component. An aircraft software part is sent to the onboard electronic distribution system from the on ground component to perform the uplink. A status of a transfer of the aircraft software part on ground component is stored.

RELATED PROVISIONAL APPLICATION

The present invention is related to and claims the benefit of priorityof provisional U.S. Patent Application Ser. No. 60/990,525 entitled“Onboard Electronic Distribution System”, filed on Nov. 27, 2007, whichis hereby incorporated by reference.

BACKGROUND INFORMATION

1. Field

The present disclosure relates generally to an improved data processingsystem and, in particular, to a method and apparatus for managingsoftware for aircraft. Still more particularly, the present disclosurerelates to a computer implemented method, apparatus, and computer usableprogram product for managing loadable software airplane parts, as wellas other documents related to the parts known as part usage assets orsimply as assets.

2. Background

Modern aircraft are extremely complex. For example, an aircraft may havemany types of electronic systems on board. A particular electronicsystem on an aircraft may also be referred to as a line replaceable unit(LRU). Each line replaceable unit may take on various forms. A linereplaceable unit may be, for example, without limitation, a flightmanagement system, an autopilot, an in-flight entertainment system, acommunications system, a navigation system, a flight controller, aflight recorder, and a collision avoidance system.

Line replaceable units may use software or programming to provide thelogic or control for various operations and functions. The software usedin these line replaceable units is commonly treated as parts in theairline industry. In particular, a software application for use in aline replaceable unit on an aircraft may also be tracked separately andreferred to as a loadable aircraft software part, or aircraft softwarepart. This software application also may be considered part of anairplane's configuration.

When an entity (i.e. an airline, maintenance, repair, and overhaulservice provider (“MRO”), or military squadron) receives an aircraft,aircraft software parts are typically already installed in the linereplaceable units in the aircraft. An airline, for example, may alsoreceive copies of these aircraft software parts in case the parts needto be reinstalled or reloaded into the line replaceable units in theaircraft that have failed and have been replaced. Further, the airlinealso may receive updates to the loadable aircraft software parts fromtime to time. These updates may include additional features not presentin the currently installed aircraft software parts, and may beconsidered upgrades to one or more line replaceable units.

The current system for managing, handling, and distributing loadableaircraft software parts is cumbersome and time consuming. Currently,aircraft software parts are stored on physical media, such as diskettes,compact discs, or digital versatile discs (DVD). An airline receives adelivery of the physical media and stores that physical media in alocation such as, for example, filing cabinets. The media also may bekept on board the aircraft in many cases.

Maintenance operations may be performed on the aircraft to install orreinstall aircraft software parts from time to time. When an aircraftsoftware part is needed, the media containing that part must be locatedand retrieved for use by maintenance personnel. This type of storage andretrieval system and process takes up both space and time.

Thus, it would be advantageous to have an improved method and apparatusfor distributing aircraft software parts that solves the above-describedproblems.

SUMMARY

In one advantageous embodiment, a computer implemented method is usedfor transferring information with the aircraft. A connection isestablished between an onboard electronic distribution system executingin an aircraft data processing system in the aircraft and an on groundcomponent. Responsive to a request for a command from the on groundcomponent made through the connection, the command for execution by theonboard electronic distribution system is identified to form anidentified command. The identified command is sent to the onboardelectronic distribution system from the on ground component. Atransaction identifier is assigned to the command. A status of atransaction associated with the command is maintained on the onboardelectronic distribution system and the on ground component using thetransaction identifier. An uplink is initiated by the on groundcomponent. An aircraft software part is sent to the onboard electronicdistribution system from the on ground component to perform the uplink.A status of a transfer of the aircraft software part on ground componentis stored.

In another advantageous embodiment, a computer implemented method isused for transferring information with an aircraft. A command isrequested from an on ground component. Responsive to receiving an uplinkcommand from the on ground component, an aircraft software partcorresponding to an uplink command is requested. The aircraft softwarepart is received from the on ground component in response to sending arequest for the aircraft software part to form a received aircraftsoftware part. The aircraft software part is stored.

In yet another advantageous embodiment, an apparatus comprises an onground component, an onboard electronic distribution system, a dataprocessing system, and an aircraft data processing system. The onboardelectronic distribution system is capable of receiving a command fromthe on ground component; requesting an aircraft software partcorresponding to an uplink command in response to receiving the uplinkcommand from the on ground component; receiving the aircraft softwarepart from the on ground component in response to sending the request forthe aircraft software part to form a received aircraft software part;and storing the aircraft software part. The on ground component executeson a data processing system. The onboard electronic distribution systemexecutes on the aircraft data processing system.

The features, functions, and advantages can be achieved independently invarious embodiments of the present disclosure or may be combined in yetother embodiments in which further details can be seen with reference tothe following description and drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features believed characteristic of the advantageousembodiments are set forth in the appended claims. The advantageousembodiments, however, as well as a preferred mode of use, furtherobjectives, and advantages thereof, will best be understood by referenceto the following detailed description of an advantageous embodiment ofthe present disclosure when read in conjunction with the accompanyingdrawings, wherein:

FIG. 1 is a diagram of a data processing environment in accordance withan illustrative embodiment;

FIG. 2 is a diagram of a data processing system in accordance with anillustrative embodiment;

FIG. 3 is a diagram illustrating an aircraft software part managementapparatus in accordance with an advantageous embodiment;

FIG. 4 is a block diagram of a software part management environment inaccordance with an advantageous embodiment;

FIG. 5 is a table illustrating modes of operation for a software partmanagement environment in accordance with an advantageous embodiment;

FIG. 6 is a diagram illustrating command types in accordance with anadvantageous embodiment;

FIG. 7 is a format for commands in accordance with an advantageousembodiment;

FIG. 8 is a message flow diagram illustrating processing of uplinkcommands in accordance with an advantageous embodiment;

FIG. 9 is a messaging diagram illustrating processing of a downlinkcommand in accordance with an advantageous embodiment;

FIG. 10 is a message flow diagram illustrating processing of a deletecommand in accordance with an advantageous embodiment;

FIG. 11 is a high level flowchart of a process used to distribute anaircraft software part in accordance with an advantageous embodiment;

FIG. 12 is a flowchart for receiving and storing aircraft software partsin accordance with an advantageous embodiment;

FIG. 13 is a flowchart of a process for distributing commands through aproxy server in accordance with an advantageous embodiment;

FIG. 14 is a flowchart of a process for receiving and distributingdownlink data through a proxy server application in accordance with anadvantageous embodiment;

FIG. 15 is a flowchart of a process for distributing aircraft softwareparts using a software maintenance tool in accordance with anadvantageous embodiment;

FIG. 16 is a flowchart of a process for receiving data using a softwaremaintenance tool in accordance with an advantageous embodiment;

FIG. 17 is a functional block diagram of a library in accordance with anadvantageous embodiment;

FIG. 18 is a diagram illustrating a file system directory layout inaccordance with an advantageous embodiment;

FIG. 19 is a block diagram illustrating an organization of commands inqueues in accordance with an advantageous embodiment;

FIG. 20 is a block diagram of an aircraft software part in accordancewith an advantageous embodiment;

FIG. 21 is a command data structure for a delete command in accordancewith an advantageous embodiment;

FIG. 22 is a diagram illustrating a command data structure for an uplinkcommand in accordance with an advantageous embodiment;

FIG. 23 is a diagram illustrating a data structure for a downlinkcommand in accordance with an advantageous embodiment;

FIG. 24 is a diagram of a user interface for dispatching commands inaccordance with an advantageous embodiment;

FIG. 25 is a diagram illustrating a user interface for viewing commandsin accordance with an advantageous embodiment;

FIG. 26 is a diagram of a user interface for viewing parts in accordancewith an advantageous embodiment;

FIG. 27 is a flowchart of a process for receiving aircraft softwareparts in a library in accordance with an advantageous embodiment;

FIG. 28 is a flowchart of a process for creating a command in accordancewith an advantageous embodiment;

FIG. 29 is a high level flowchart of a process for managing aircraftsoftware parts in accordance with an advantageous embodiment;

FIG. 30 is a flowchart of a process for dispatching command structuresin accordance with an advantageous embodiment;

FIG. 31 is a flowchart of a process for dispatching command files inaccordance with an advantageous embodiment;

FIG. 32 is a flowchart of a process for dispatching parts in accordancewith an advantageous embodiment;

FIG. 33 is a flowchart of a process for dequeuing commands in accordancewith an advantageous embodiment;

FIG. 34 is a diagram illustrating data flow in a proxy serverapplication in accordance with an advantageous embodiment;

FIG. 35 is a diagram illustrating a proxy server application inaccordance with an advantageous embodiment;

FIGS. 36-39 are diagrams illustrating data structures in accordance withan advantageous embodiment;

FIG. 40 is a diagram of a proxy server file system directory structurein accordance with an advantageous embodiment;

FIG. 41 is a flowchart of a process for receiving information from alibrary in accordance with an advantageous embodiment;

FIG. 42 is a flowchart of a process for sending downlink files to alibrary in accordance with an advantageous embodiment;

FIG. 43 is a flowchart of a process for sending event files to a libraryin accordance with an advantageous embodiment;

FIG. 44 is a flowchart of a process for sending information to anaircraft in accordance with an advantageous embodiment;

FIG. 45 is a flowchart of a process for receiving aircraft softwareparts in accordance with an advantageous embodiment;

FIG. 46 is a flowchart of a process for receiving command statusinformation from an aircraft in accordance with an advantageousembodiment;

FIG. 47 is a flowchart of a process for receiving downlink files inaccordance with an advantageous embodiment;

FIG. 48 is a flowchart of a process for receiving status informationfrom a software maintenance tool in accordance with an advantageousembodiment;

FIG. 49 is a flowchart of a process for sending information to asoftware maintenance tool in accordance with an advantageous embodiment;

FIG. 50 is a flowchart of a process for sending lists of aircraftsoftware parts to a software maintenance tool in accordance with anadvantageous embodiment;

FIG. 51 is a flowchart of a process for receiving downlink files from asoftware maintenance tool in accordance with an advantageous embodiment;

FIG. 52 is a flowchart of a process for receiving event log files from asoftware maintenance tool in accordance with an advantageous embodiment;

FIG. 53 is a diagram illustrating data flow and a software maintenancetool in accordance with an advantageous embodiment;

FIG. 54 is a block diagram of a software maintenance tool in accordancewith an advantageous embodiment;

FIG. 55 is a diagram of commands and command resource tables inaccordance with an advantageous embodiment;

FIG. 56 is a diagram of partial downlink data in accordance with anadvantageous embodiment;

FIG. 57 is a diagram of a downlinks table in accordance with anadvantageous embodiment;

FIG. 58 is a diagram of a software maintenance tool file systemdirectory structure in accordance with an advantageous embodiment;

FIG. 59 is a diagram illustrating interface components implemented in asoftware maintenance tool in accordance with an advantageous embodiment;

FIGS. 60-65 are example implementations of user interfaces for userinterface components in accordance with an advantageous embodiment;

FIG. 66 is a diagram illustrating data flow through a softwaremaintenance tool in sending commands and aircraft software parts to anaircraft in accordance with an advantageous embodiment;

FIG. 67 is a diagram illustrating data flow in a software maintenancetool processing downlinked files in accordance with an advantageousembodiment;

FIG. 68 is a diagram illustrating data flow and logging importing eventsby a software maintenance tool in accordance with an advantageousembodiment;

FIG. 69 is a diagram illustrating data flow in a software maintenancetool retrieving parts from a library in accordance with an advantageousembodiment;

FIG. 70 is a diagram illustrating data flow in a software maintenancetool during retrieving and creating of commands in accordance with anadvantageous embodiment;

FIG. 71 is a diagram illustrating uploading of aircraft software partsfrom alternative sources in accordance with an advantageous embodiment;

FIG. 72 is a high level flowchart of a process for managing aircraftsoftware parts in accordance with an advantageous embodiment;

FIG. 73 is a more detailed flowchart of a process for managing aircraftsoftware parts in accordance with an advantageous embodiment;

FIG. 74 is a flowchart of a process for sending aircraft software partsfrom a software maintenance tool to an onboard electronic distributionsystem in accordance with an advantageous embodiment;

FIG. 75 is a flowchart of a process for receiving downlink data inaccordance with an advantageous embodiment;

FIG. 76 is a diagram of components used to transfer information with anaircraft in accordance with an advantageous embodiment;

FIG. 77 is a message flow diagram illustrating message flow used to pollfor a command in accordance with an advantageous embodiment;

FIGS. 78-79 are message flow diagrams illustrating the sending of statusinformation in accordance with an advantageous embodiment;

FIG. 80 is a message flow diagram for downlinking data in accordancewith an advantageous embodiment;

FIG. 81 is a diagram illustrating message flow when the file is onlypartially delivered in accordance with an advantageous embodiment;

FIG. 82 is a message flow diagram illustrating an uplink process inaccordance with an advantageous embodiment;

FIG. 83 is a diagram illustrating message flow in an uplink process inaccordance with an advantageous embodiment;

FIG. 84 is a flowchart of a process for uplinking data in accordancewith an advantageous embodiment;

FIG. 85 is a flowchart of a process for downlinking data in accordancewith an advantageous embodiment;

FIG. 86 is a diagram illustrating a crate tool in accordance with anadvantageous embodiment;

FIG. 87 is a diagram illustrating a crate tool in accordance with anadvantageous embodiment;

FIG. 88 is a message flow diagram illustrating the processing of a cratein accordance with an advantageous embodiment;

FIG. 89 is a diagram illustrating one implementation of a user interfacefor a crate tool in accordance with an advantageous embodiment;

FIG. 90 is a diagram illustrating data flow in inspecting and unpackingcrates in accordance with an advantageous embodiment;

FIG. 91 is a diagram illustrating the data flow in creating a crate inaccordance with an advantageous embodiment; and

FIG. 92 is a flowchart of a process for processing a received crate inaccordance with an advantageous embodiment.

DETAILED DESCRIPTION

With reference now to the figures and, in particular, with reference toFIG. 1, an exemplary diagram of a data processing environment isprovided in which the advantageous embodiments may be implemented. Itshould be appreciated that FIG. 1 is only exemplary and is not intendedto assert or imply any limitation with regard to the environments inwhich different embodiments may be implemented. As used herein, the termexemplary refers to an example and not necessarily an idealimplementation. Many modifications to the depicted environments may bemade.

Turning now to FIG. 1, a diagram illustrating a network data processingsystem in which a software part management environment may beimplemented is depicted in accordance with an advantageous embodiment.In this example, network data processing system 100 is a network dataprocessing system in which information may be transferred betweenaircraft network 101 and ground network 103. This information mayinclude, for example, without limitation, commands, aircraft softwareparts, downlink data, error logs, usage history, flight data, statusinformation, and manuals. Ground network 103 includes networks andcomputers located on the ground. Aircraft network system 101 is anetwork and computers located on an aircraft.

In these examples, commands may be generated on library 102 located onlibrary server computer 104. Library server computer 104 and other dataprocessing systems, such as server computers 105 and 106, connect tointranet 108.

These commands may be distributed to on ground component (OGC) 109 onproxy server computer 110 through a network, such as Internet 112.Intranet 108 and Internet 112 may include connections such as, forexample, wires, fiber optic cables, or wireless communications links.Proxy server computer 110 may be located in a facility, such as airport114. Proxy servers, such as proxy server computer 110, may be located atother airports and other locations, such as maintenance locations. Proxyserver computer 110 provides for temporary part storage 111 for commandsand parts received from library 102.

The commands and aircraft software parts also may be sent to softwaremaintenance tools on portable computers, such as software maintenancetool 115 on maintenance laptop 116. Proxy server computer 110 andmaintenance laptop 116 are referred to collectively as ground tools. Aground tool may be any data processing system that is configured with anappropriate application to transfer information, such as commands,aircraft software parts, and downlink data.

Proxy server computer 110 may connect to aircraft 118 through varioustypes of connections or links. For example, wireless unit 120 mayestablish wireless connection 122 with wireless unit 124 on aircraft118. Wireless unit 124 connects to open data network 126 in aircraft118. Maintenance laptop 134 has software maintenance tool 136 and onground component (OGC) 138 and may communicate with aircraft 118establishing communications link 140 with cabin wireless access unit142. Communications link 140 is a wireless virtual private networktunnel. Cabin wireless access unit 142 connects to open data network 126in these examples. Open data network 126 provides an interface forvarious communications links, such as wireless link 122. Additionally,satellite unit 128 connected to proxy server computer 110 at airport 114may establish satellite link 130 with satellite unit 132, which is alsoconnected to open data network 126.

Open data network 126 connects to aircraft data processing system 144,which contains onboard electronic distribution system (OBEDS) 146.Storage device 148 also is located in aircraft data processing system144. Storage device 148 provides a location to store information, suchas aircraft parts. Aircraft data processing system 144 also includesfile transfer system (FTS) 150, onboard storage manager (OSM) 152,onboard data load function (ODLF) 154, and signer-crater module (SCM)156. In these examples, signer-crater module 156 may be implemented as aJava® library compiled into onboard electronic distribution system 146.Also, aircraft data processing system 144 may take the form of a crewinformation system/maintenance system computer.

File transfer system 150 is used to transfer files from storage device148 to a line replaceable unit. Onboard storage manager 152 managesinformation stored in storage device 148. Onboard data load function 154is a software component used to load aircraft software parts onto linereplaceable units. Signer-crater module 156 is used to process incomingcrates and store the contents of those crates in storage device 148.Additionally, signer-crater module 156 may crate download data fordownloading to proxy server computer 110.

All command processing, in these examples, is initiated by onboardelectronic distribution system 146 located in aircraft data processingsystem 144. Onboard electronic distribution system 146 monitors theair-to-ground link status and determines whether a communications linkhas been established. If a link becomes available, onboard electronicdistribution system 146 connects to a ground data processing system viathe link.

In other advantageous embodiments, maintenance laptop 158 may establishcommunications link 164 with isolated data network 166. Maintenancelaptop 158 has software maintenance tool 160 and on ground component162. Communications link 164 may be a wired connection. The linereplaceable units may be, for example, central server module (CSM) 168,electronic flight bag (EFB) 170, and cabin services system (CSS) 172.Central server module 168 provides common networking functions for thedifferent networks in aircraft 118. These services include, for example,packet routing, firewall, and wireless access. Cabin services system 172provides applications to control systems in the aircraft, such aslighting, cabin doors, and address system.

If onboard electronic distribution system 146 establishes a connectionto a ground device, onboard electronic distribution system 146 requestsa list of commands queued or stored for aircraft 118. Onboard groundcomponents 109, 138, or 162, on data processing systems, such as proxyserver computer 110, maintenance laptop 134, and/or maintenance laptop158, communicate with onboard electronic distribution system 146 onaircraft data processing system 144 in these examples. This type ofsoftware component provides an application program interface to theground tool to uplink commands and aircraft software parts to aircraft118 as well as downlinking data or files.

The illustration of particular components and configurations in networkdata processing system 100 are not meant to imply architecturallimitations to the manner in which different embodiments may beimplemented. For example, although only a single aircraft is shown inaircraft network 101, multiple aircraft may be present within aircraftnetwork 101. As another example, airline network 108 in ground network103 may connect to computers, such as proxy server computer 110, atairports, such as airport 114, through other types of networks otherthan Internet 112. For example, a wide area network (WAN) may be used inplace of, or in conjunction with, Internet 112.

Turning now to FIG. 2, a diagram of a data processing system is depictedin accordance with an advantageous embodiment. In these examples, dataprocessing system 200 is an example of a data processing system that maybe used to implement data processing systems, such as library servercomputer 104, maintenance laptop 116, proxy server computer 110,maintenance laptop 134, maintenance laptop 158, and aircraft dataprocessing system 144 in FIG. 1.

In this illustrative example, data processing system 200 includescommunications fabric 202, which provides communications betweenprocessor unit 204, memory 206, persistent storage 208, communicationsunit 210, input/output (I/O) unit 212, and display 214.

Processor unit 204 serves to execute instructions for software that maybe loaded into memory 206. Processor unit 204 may be a set of one ormore processors or may be a multi-processor core, depending on theparticular implementation. Further, processor unit 204 may beimplemented using one or more heterogeneous processor systems in which amain processor is present with secondary processors on a single chip. Asanother illustrative example, processor unit 204 may be a symmetricmulti-processor system containing multiple processors of the same type.

Memory 206, in these examples, may be, for example, a random accessmemory or any other suitable volatile or non-volatile storage device. Astorage device is hardware that is capable of storing program code in afunctional form for execution by a processor or other hardware device.Persistent storage 208 may take various forms depending on theparticular implementation. For example, persistent storage 208 maycontain one or more components or devices. For example, persistentstorage 208 may be a hard drive, a flash memory, a rewritable opticaldisk, a rewritable magnetic tape, or some combination of the above. Themedia used by persistent storage 208 also may be removable. For example,a removable hard drive may be used for persistent storage 208.

Communications unit 210, in these examples, provides for communicationswith other data processing systems or devices. In these examples,communications unit 210 is a network interface card. Communications unit210 may provide communications through the use of either or bothphysical and wireless communications links.

Input/output unit 212 allows for input and output of data with otherdevices that may be connected to data processing system 200. Forexample, input/output unit 212 may provide a connection for user inputthrough a keyboard and mouse. Further, input/output unit 212 may sendoutput to a printer. Display 214 provides a mechanism to displayinformation to a user.

Instructions for the operating system and applications or programs arelocated on persistent storage 208. These instructions may be loaded intomemory 206 for execution by processor unit 204. The processes of thedifferent embodiments may be performed by processor unit 204 usingcomputer implemented instructions, which may be located in a memory,such as memory 206. These instructions are referred to as program code,computer usable program code, or computer readable program code that maybe read and executed by a processor in processor unit 204. The programcode in the different embodiments may be embodied on different physicalor tangible computer readable media, such as memory 206 or persistentstorage 208.

Program code 216 is in a functional form and located on computerreadable media 218 and may be loaded onto or transferred to dataprocessing system 200 for execution by processor unit 204. Program code216 and computer readable media 218 form computer program product 220 inthese examples. In one example, computer readable media 218 may be in atangible form such as, for example, an optical or magnetic disc that isinserted or placed into a drive or other device that is part ofpersistent storage 208 for transfer onto a storage device, such as ahard drive that is part of persistent storage 208. In a tangible form,computer readable media 218 also may take the form of a persistentstorage, such as a hard drive or a flash memory, which is connected todata processing system 200. The tangible form of computer readable media218 is also referred to as computer recordable storage media.

Alternatively, program code 216 may be transferred to data processingsystem 200 from computer readable media 218 through a communicationslink to communications unit 210 and/or through a connection toinput/output unit 212. The communications link and/or the connection maybe physical or wireless in the illustrative examples. The computerreadable media also may take the form of non-tangible media, such ascommunications links or wireless transmissions containing the programcode.

The different components illustrated for data processing system 200 arenot meant to provide architectural limitations to the manner in whichdifferent embodiments may be implemented. The different illustrativeembodiments may be implemented in a data processing system includingcomponents in addition to, or in place of, those illustrated for dataprocessing system 200. Other components shown in FIG. 2 can be variedfrom the illustrative examples shown.

For example, a bus system may be used to implement communications fabric202 and may be comprised of one or more buses, such as a system bus oran input/output bus. Of course, the bus system may be implemented usingany suitable type of architecture that provides for a transfer of databetween different components or devices attached to the bus system.Additionally, a communications unit may include one or more devices usedto transmit and receive data, such as a modem or a network adapter.Further, a memory may be, for example, memory 206 or a cache such asfound in an interface and memory controller hub that may be present incommunications fabric 202.

The different advantageous embodiments provide a computer implementedmethod, apparatus, and computer usable program product for managingaircraft software parts.

With reference now to FIG. 3, a diagram illustrating an aircraftsoftware part management apparatus is depicted in accordance with anadvantageous embodiment. In this example, aircraft software partmanagement apparatus 300 includes receiving module 302, library 304,proxy server application 306, software maintenance tool 308, and onboardelectronic distribution system 310.

Receiving module 302 is capable of receiving an aircraft software partfrom a source and sending the aircraft software part to library 304 forstorage. The source may include, for example, an aircraft manufacturer,a software vendor, a library supplier, or an airline.

In these examples, library 304 is located on a data processing system,such as library server computer 102 in FIG. 1. Library 304 provides astorage system for the aircraft software part. Also, library 304 may beused to manage the aircraft software parts. The management of the partsmay include, for example, without limitation, organizing aircraftsoftware parts, deleting aircraft software parts, and distributingaircraft software parts. Security and versioning control processes maybe used to manage the aircraft software parts.

Proxy server application 306 may be located on the same data processingsystem or a different data processing system, depending on theparticular implementation. Proxy server application 306 is incommunication with library 304 and is capable of serving differentaircraft clients.

Software maintenance tool 308 may be a software maintenance tool locatedon a portable computer that provides an alternate route to send theaircraft software part to onboard electronic distribution system 310from library 304. Software maintenance tool 308 may receive the aircraftsoftware part directly from library 304 or through proxy serverapplication 306, depending on the particular implementation.

Onboard electronic distribution system 310 is an example of an aircraftclient located on an aircraft. Onboard electronic distribution system310 is a software client that executes on a data processing system onthe aircraft. Onboard electronic distribution system 310 may receive anaircraft software part for the aircraft from library 304 through proxyserver application 306. After the aircraft software part has beenreceived by onboard electronic distribution system 310, the aircraftsoftware part may be installed in a line replaceable unit for use.

In addition to using aircraft software part management apparatus 300 todistribute aircraft software parts to an aircraft, this apparatus alsomay be used to receive data generated by the aircraft. This data also isreferred to as downlink data. For example, a flight recorder maygenerate data describing different events occurring during a flight.This data may be downlinked through onboard electronic distributionsystem 310 through proxy server application 306 and/or softwaremaintenance tool 308 back to library 304 for later use and analysis.This data also may include configuration data about the aircraftsoftware part, the line replaceable unit, or the airplane configuration.

With reference now to FIG. 4, a block diagram of a software partmanagement environment is depicted in accordance with an advantageousembodiment. Software part management environment 400 is an example ofone implementation for aircraft software part management apparatus 300in FIG. 3.

In this example, crate tool 402 executes on computer 404. Crate tool 402is an example of one implementation of receiving module 302 in FIG. 3.Library 406 is located on server computer 410. Library 406 is an exampleof one implementation of library 304 in FIG. 3. Proxy server application412 executes on server computer 414 and is an example of animplementation of proxy server application 306 in FIG. 3. Softwaremaintenance tool 416 executes on portable computer 418. Softwaremaintenance tool 416 is an example of software maintenance tool 308 inFIG. 3. Onboard electronic distribution system 420 runs on aircraftcomputer 422 on aircraft 424. Onboard electronic distribution system 420is an example of one implementation for onboard electronic distributionsystem 310 in FIG. 3.

In these examples, crate tool 402 may receive and process softwareparts, such as aircraft software part 426 in crate 428. Crate 428 is apackaging system for aircraft software part 426 and is not a physicalobject. Crate 428, in these examples, is a file that contains aircraftsoftware part 426. Crate 428 may be, for example, a zip file using a zipfile format.

A zip file format is a data compression and archival format in which thezip file may contain one or more files that have been compressed. Otherexamples of packaging systems for files include, for example, JAVA®archive (JAR) files. These files also may be encrypted or digitallysigned, depending on the particular implementation. Of course, any typeof mechanism that provides a wrapper for aircraft software part 426 maybe used. In these examples, the wrapper is a security wrapper that isdesigned to meet various security requirements that may be set orrequired for aircraft software part 426.

Aircraft software part 426 may be a software application for use on adata processing system in the aircraft in these examples. The dataprocessing system may be one located within line replaceable units 430in aircraft 424. The application may include a set of files. The set offiles may include, for example, one or more programs, data files,libraries, configuration files, or other information or code. As usedherein, “a set” refers to one or more items. As an example, a set ofaircraft software parts is one or more aircraft software parts, and aset of commands is one or more commands.

Crate tool 402 receives crate 428 and processes crate 428 to storeaircraft software part 426 in aircraft software parts 432 in library406. This processing may include, for example, validating signatures forcrate 428 and aircraft software part 426. This validation may beperformed to ensure that no corruption or errors has occurred in crate428 or aircraft software part 426. The different parts stored withinlibrary 406 may be distributed to an aircraft, such as aircraft 424,through the proxy server application.

Library 406 provides a component within software part managementenvironment 400 to perform various management operations on aircraftsoftware parts 432. These management operations may include, forexample, without limitation, distributing aircraft software parts to anaircraft, organizing aircraft software parts, deleting aircraft softwareparts, receiving data from aircraft on which aircraft software parts arepresent, and receiving new aircraft software parts.

Proxy server application 412 may obtain a set of aircraft software partsfrom aircraft software parts 432 and send those parts to onboardelectronic distribution system 420. Proxy server application 412 is incommunication with onboard electronic distribution system 420 through acommunications link. This communications link may take various forms.For example, a wireless communications link may be used. In this manner,aircraft parts and data may be exchanged while the aircraft is on groundor even in flight. In other examples, server computer 414 may beconnected to aircraft computer 422 through a wired link in a network.

Onboard electronic distribution system 420 processes the set of aircraftparts and stores these parts as aircraft software parts 434 withinstorage device 436 on aircraft computer 422. As needed, an aircraftsoftware part from aircraft software parts 434 may be installed in linereplaceable units 430. Data, such as an aircraft software part, manuals,documentation, and commands, sent to the aircraft are referred to asuplink data.

Additionally, data may flow in the other direction from aircraft 424through proxy server application 412 back to library 406. This type ofdata is referred to as downlink data. In these examples, linereplaceable units 430 may generate downlink data 438, which istemporarily stored in storage device 436. Onboard electronicdistribution system 420 may send downlink data 438 to proxy serverapplication 412. In turn, proxy server application 412 sends downlinkdata 438 to library 406 for storage. This data may then be processed andanalyzed. This data also may include, for example, the status ofsoftware on an aircraft. This status information may be used to send anoperator to the aircraft to initiate loading and installation of theline replaceable unit on the aircraft.

Additionally, software maintenance tool 416 on portable computer 418provides an alternative route for transferring aircraft software partsand downlink data. Portable computer 418 may be, for example, a laptopcomputer. Portable computer 418 may obtain an aircraft software partfrom aircraft software parts 432 through proxy server application 412 ordirectly from library 406, depending on the particular implementation.Thereafter, portable computer 418 may be transported to aircraft 424 andestablish a communications link with onboard electronic distributionsystem 420 on aircraft computer 422 to send the aircraft software partto onboard electronic distribution system 420.

This type of distribution of aircraft software parts is especiallyuseful when network connections or communications links cannot beestablished between server computer 414 and aircraft computer 422 onaircraft 424. This type of situation may occur depending on the type ofequipment available at an airport or maintenance facility. Further, insome cases, the network or communications systems providingcommunications links may be temporarily unavailable or require repair.In this manner, software maintenance tool 416 may transfer an aircraftsoftware part to onboard electronic distribution system 420. Further,software maintenance tool 416 may also receive downlink data 438 whilein communication with onboard electronic distribution system 420.

In this manner, the different advantageous embodiments provide acomputer implemented method, apparatus, and computer usable program codefor managing aircraft software parts. Further, the differentadvantageous embodiments also may provide for the transfer of data froman aircraft to a facility or location for later analysis or review.

Turning now to FIG. 5, a table illustrating modes of operation for asoftware part management environment is depicted in accordance with anadvantageous embodiment. In this example, table 500 illustrates some ofthe different modes of operation that may occur within software partmanagement environment 400 in FIG. 4. In these examples, the differentmodes of operation include receive and store parts mode 502, distributecommands mode 504, distribute parts mode 506, and receive downlink datamode 508. These different modes of operations illustrated in table 500are ones that may occur in one or more components within software partmanagement environment 400 in FIG. 4.

In receive and store parts mode 502, aircraft software parts may bereceived and stored within library 406 in FIG. 4. Distribute commandsmode 504 is used to send commands to the aircraft. These commands maybe, for example, to uplink data. This data may include, for example,sending aircraft software parts to an aircraft. The uplink data also mayinclude commands to send documentation or other information to anaircraft. Distribute parts mode 506 is the mode of operation in whichaircraft software parts are actually sent to the aircraft. Receivedownlink data mode 508 is a mode of operation in which data is sent fromvarious components in an aircraft to the library in the software partmanagement environment.

With reference now to FIG. 6, a diagram illustrating command types isdepicted in accordance with an advantageous embodiment. In this example,command types 600 include uplink command 602, downlink command 604, anddelete command 606. Uplink command 602 is used to send information froma library to an aircraft. This information may include, for example,aircraft software parts, configuration information, and other data.Downlink command 604 is used to initiate the transfer of data from anaircraft to a library. This information may include, for example, statusinformation on the uplinking of aircraft software parts and reports ofconfiguration of line replaceable units on the aircraft. Delete command606 is employed to delete information on the aircraft. For example,delete command 606 may be used to delete a selected aircraft softwarepart on an aircraft. In these examples, these different commands aresent to the aircraft in a crate.

Turning now to FIG. 7, a format for commands is depicted in accordancewith an advantageous embodiment. In this example, command 700 takes theform of an extensible markup language (XML) data structure. Command 700,in this example, is an uplink command.

Message identifier element 702 in command 700 provides a uniqueidentifier for the command. Type element 704 indicates the type ofcommand. In this example, the type of command is identified as an uplinkcommand. System element 706 identifies the target system for thecommand. Application identifier element 708 identifies the applicationon the target system to receive the command.

Link label element 710 identifies the type of network link used totransfer the command from the library to the aircraft. For example, thelink may be a wired link or a wireless link. Server address element 712identifies the address of the identified device. Data type element 714provides an identification of the type of information that is subject tothe command. Resource type element 716 identifies the particular filethat is subject to the command.

Turning now to FIG. 8, a message flow diagram illustrating processing ofuplink commands is depicted in accordance with an advantageousembodiment. In this example, processing of an uplink command involvesground system 800, onboard electronic distribution system (OBEDS) 802,file transfer system (FTS) 804, and line replaceable unit (LRU) 806. Inthese examples, ground system 800 is, for example, a proxy serverapplication on a computer or a software maintenance tool located on alaptop computer.

The process begins by onboard electronic distribution system 802establishing a connection with ground system 800 (message M1). Inresponse to the connection, ground system 800 makes the next commandavailable. In this example, the next command is an uplink command.Ground system 800 sends the uplink command to onboard electronicdistribution system 802 (message M2). Onboard electronic distributionsystem 802 checks the signature for the uplink command.

Thereafter, onboard electronic distribution system 802 sends a requestfor the source to ground system 800 (message M3). Ground system 800makes the crate corresponding to the request available for transfer. Therequest in message M3 is identified from the uplink command received inmessage M2.

Onboard electronic distribution system 802 uplinks the crate from groundsystem 800 (message M4). After receiving the crate, onboard electronicdistribution system 802 validates the signatures on the crate. Thisvalidation includes validating the signature on the crate as well as thesignatures for the aircraft software part.

Thereafter, onboard electronic distribution system 802 sends a transferrequest to file transfer system 804 (message M5). In response, filetransfer system 804 transfers the aircraft software part to linereplaceable unit 806 (message M6).

The status is then transferred from file transfer system 804 to onboardelectronic distribution system 802 (message M7).

Turning now to FIG. 9, a messaging diagram illustrating processing of adownlink command is depicted in accordance with an advantageousembodiment. In this example, the same components as in FIG. 8 arepresent for processing a downlink command. In this example, onboardelectronic distribution system 802 connects to ground system 800(message N1). Ground system 800 makes the next command available forprocessing.

A downlink command is sent to onboard electronic distribution system 802(message N2). Onboard electronic distribution system 802 sends a requestto file transfer system 804 to send the downlink command to linereplaceable unit 806 (message N3). In turn, file transfer system 804sends the downlink command to line replaceable unit 806 (message N4).Line replaceable unit 806 processes the command and then sends downlinkdata to file transfer system 804 (message N5). File transfer system 804sends a request to onboard electronic distribution system 802 to senddownlink data to ground system 800 (message N6). In response, onboardelectronic distribution system 802 crates and signs the downlink data.Additionally, onboard electronic distribution system 802 also addsmetadata to the crate. Thereafter, onboard electronic distributionsystem 802 sends the crate to ground system 800 (message N7).

Turning now to FIG. 10, a message flow diagram illustrating processingof a delete command is depicted in accordance with an advantageousembodiment. The same components as depicted in FIGS. 8 and 9 are used toprocess a delete command. The process begins with onboard electronicdistribution system 802 connecting to ground system 800 (message O1). Inresponse, ground system 800 makes the next command for onboardelectronic distribution system 802 available. Onboard electronicdistribution system 802 receives the delete command (message O2).

Thereafter, onboard electronic distribution system 802 checks thesignature for the command. If the signature is valid, onboard electronicdistribution system 802 sends a request to file transfer system 804 tosend the delete command to line replaceable unit 806 (message O3). Inthese examples, the only time the signature on the command is checked isif the command is issued from the proxy server. The same occurs for thedownlink command. Thereafter, file transfer system 804 sends the deletecommand to line replaceable unit 806 (message O4).

In response to receiving the delete command, line replaceable unit 806deletes the resource identified by the delete command.

File transfer system 804 sends a request to onboard electronicdistribution system 802 to send the status to ground system 800 (messageO5). This status indicates whether the resource was successfully deletedby line replaceable unit 806. In response to receiving this request,onboard electronic distribution system 802 crates and signs the status.Thereafter, the crate is sent to ground system 800 (message O6).

Turning now to FIG. 11, a high level flowchart of a process used todistribute an aircraft software part is depicted in accordance with anadvantageous embodiment. The process illustrated in FIG. 11 is anexample of a process that may be found in software part managementenvironment 400 in FIG. 4 to install an aircraft software part on anaircraft.

The process begins by storing an aircraft software part in a library(operation 1100). In these examples, the library is a software aircraftmanagement component, such as library 406 in FIG. 4. The process thenidentifies an aircraft to receive the aircraft software part to form anidentified aircraft (operation 1102). In operation 1102, an operator ofthe library may select aircraft software parts for distribution to a setof aircraft. In other embodiments, the target aircraft for aircraftsoftware parts may be preselected through a communication or filereceived from another system.

Thereafter, the aircraft software part is sent to a proxy serverapplication (operation 1104) in the form of an uplink command. The proxyserver application sends the uplink command and the aircraft softwarepart to an onboard electronic distribution system on the identifiedaircraft (operation 1106), with the process terminating thereafter.

Turning now to FIG. 12, a flowchart for receiving and storing aircraftsoftware parts is depicted in accordance with an advantageousembodiment. The process illustrated in FIG. 12 may be implemented insoftware part management environment 400 in FIG. 4. This process is anexample of steps that may be performed in receive and store parts mode502 in FIG. 5.

The process begins with a crate tool receiving a crate (operation 1200).This tool may be, for example, crate tool 402 in FIG. 4. In thisexample, the crate contains an aircraft software part that may berequested from a point of origin, such as a manufacturer of the aircraftor line replaceable units in the aircraft. The aircraft software partmay be received in response to a notification of the availability of theaircraft software part and delivered through some transport mechanism.The crate may be received on a physical or tangible media, such as acompact disc, flash memory, or digital versatile disc. In otherembodiments, the crate may be received through a transmission media,such as a communications link over a network.

The crate tool validates and unpacks the crate (operation 1202). In thisoperation, a notification is generated if the signature is invalid orthe digest does not match the one calculated by the crate tool. If noproblems are detected, the crate is unpacked into various locations foradditional processing. Next, the crate tool validates the signature forthe aircraft software part (operation 1204). If the signature is invalidor the digest for the aircraft software part does not match the onecalculated, a notification is generated. If no problems are detected,the part is now ready to be signed after the contents of the crate havebeen validated or verified.

The crate tool then inspects the crate contents (operation 1206). Inthis operation, the contents of the crate may be displayed for aninspector to verify the contents. In other embodiments, this operationmay be performed automatically for a comparison of the contents with afile or configuration information identifying the expected contents ofthe crate.

Once the contents have been verified, the crate tool signs the aircraftsoftware part with the airline's signature (operation 1208). Dependingon the implementation, another entity's signature may be used. Forexample, the signature may be that of a customer or other party thatmanages the library. If no errors occur in signing the aircraft softwarepart, the part is ready for storage.

Thereafter, the crate tool places the aircraft software part into alibrary (operation 1210), with the process terminating thereafter. Thisoperation involves moving the aircraft software part from its currentlocation on the file system to the storage area for the librarycontaining the different aircraft software parts. In these examples,this library may be, for example, library 406 in FIG. 4.

Referring to FIG. 13, a flowchart of a process for distributing commandsthrough a proxy server is depicted in accordance with an advantageousembodiment. The process illustrated in FIG. 13 may be implemented insoftware part management environment 400 in FIG. 4. In particular, thisprocess is an example of one executed during distribute commands mode504 in FIG. 5.

The process begins by the proxy server application receiving andprocessing queued commands (operation 1300). In these examples, queuedcommands are sent in crates, referred to as command packages. The cratesare processed and sent to appropriate aircraft command queues in thelibrary. The proxy server application may access and retrieve the queuedcommands from queues in the library. If these commands include uplinkcommands, crated aircraft software parts also are placed into localinventory of the proxy server. In these examples, the commands areplaced into crates for distribution to the proxy server.

Thereafter, the proxy server application connects to the onboardelectronic distribution system on the aircraft (operation 1302). Theproxy server application may connect to multiple aircraft at the sametime. In these examples, the aircraft connects to the proxy serverapplication through a wireless connection or communications link. Oncethe communications link is established, information may flow between theproxy server application and the onboard electronic distribution system.This information may include, for example, commands, data, aircraftsoftware parts, configuration files, manuals, and status information.

The proxy server application then automatically transfers the cratecommands for the aircraft to the onboard electronic distribution system(operation 1304). In these examples, the crate commands designated forthe aircraft are available for retrieval by the onboard electronicdistribution system.

The onboard electronic distribution system reads the commands andexecutes the commands (operation 1306). In these examples, the onboardelectronic distribution system polls the command queue on the proxyserver application and retrieves each command for the aircraft onecommand at a time. The onboard electronic distribution system thenverifies the crated commands (operation 1308). If the crate is verified,the command is passed on to the designated system and application.Thereafter, the onboard electronic distribution system returns thestatus of the transfer for the commands (operation 1310), with theprocess terminating thereafter.

Turning next to FIG. 14, a flowchart of a process for receiving anddistributing downlink data through a proxy server application isdepicted in accordance with an advantageous embodiment. The processillustrated in FIG. 14 may be implemented in software part managementenvironment 400 in FIG. 4. In particular, the process illustrated inFIG. 14 is an example of operations that occur during receive downlinkdata mode 508 in FIG. 5.

The process begins with the proxy server application connecting to theonboard electronic distribution system on an aircraft (operation 1400).Thereafter, the proxy server application receives the downlink of thedata (operation 1402). In these examples, the onboard electronicdistribution system generates a downlink for each item in the queuecontaining downlink data.

Thereafter, the proxy server application places the downlink data in alocal inventory (operation 1404). This downlink data is stored fortransfer back to the library based on some event. In these examples, theevent may be a period event, such as the expiration of a timer. In otherexamples, the event may be a non-period event, such as a requestgenerated by a user. Afterwards, the proxy server application sends thedownlink data to the library (operation 1406), with the processterminating thereafter. In operation 1406, the downlink data is placedin a directory for later use or analysis.

Turning now to FIG. 15, a flowchart of a process for distributingaircraft software parts using a software maintenance tool is depicted inaccordance with an advantageous embodiment. The process illustrated inFIG. 15 may be implemented in software part management environment 400in FIG. 4. The different operations in this process are examples ofoperations that occur during distribute parts mode 506 in FIG. 5.

The process begins with the software maintenance tool connecting to thenetwork (operation 1500). This is the network in which the library ispresent. In this example, parts are not present and located on thesoftware maintenance tool. Next, the software maintenance tool retrievesa set of uplink commands and crates with aircraft software parts(operation 1502).

Thereafter, the software maintenance tool disconnects from the network(operation 1504). The software maintenance tool is then moved andconnected to the onboard electronic distribution system on the aircraft(operation 1506). In these examples, the connection requires a humanoperator to initiate the connection. The software maintenance toolautomatically transfers the set of uplink commands to the onboardelectronic distribution system (operation 1508). In these examples, thecommands are sent to the onboard electronic distribution system onecommand at a time. Each time a command is sent within operation 1508, acheck is made as to whether the onboard electronic distribution systemis done uplinking the command or other information before sending thenext command.

The onboard electronic distribution system reads the set of commands andreceives the set of crates containing the aircraft software part(operation 1510). In these examples, each command in the set of commandsis retrieved one at a time by the onboard electronic distribution systemfrom the software maintenance tool. The onboard electronic distributionsystem verifies the set of crates (operation 1512). If the crates areverified, the aircraft software parts are then passed on for storage anddistribution in the aircraft.

Then, the onboard electronic distribution system returns a status of thetransfer to the software maintenance tool (operation 1514). The softwaremaintenance tool then returns the status of the transfer (operation1516), with the process terminating thereafter. In this example, thesoftware maintenance tool returns the status to a source of the aircraftsoftware part, such as a library or proxy server application.

In these examples, the uplink commands may be manually added rather thanautomatically received from the library. For example, an operator of thesoftware maintenance tool may select aircraft software parts fortransfer to an aircraft. This selection results in the softwaremaintenance tool generating the appropriate commands to transfer theaircraft software parts. The process still receives crates for theaircraft software parts.

In this type of implementation, however, the process proceeds fromoperation 1508 to receive a selection of the aircraft software part(operation 1518). This selection is based on user input in theseexamples. Thereafter, the software maintenance tool issues an uplinkcommand to the onboard electronic distribution system (operation 1520).This command may be placed in a command queue for the onboard electronicdistribution system to retrieve.

Turning now to FIG. 16, a flowchart of a process for receiving datausing a software maintenance tool is depicted in accordance with anadvantageous embodiment. The process illustrated in FIG. 16 may beimplemented using software part management environment 400 in FIG. 4.The operations illustrated in FIG. 16 are examples of operations thatmay occur during receive downlink data mode 508 in FIG. 5.

The process begins with the software maintenance tool connecting to theonboard electronic distribution system (operation 1600). The softwaremaintenance tool receives a downlink of data from the onboard electronicdistribution system (operation 1602). The onboard electronicdistribution system initiates a downlink for each item within its queueof downlink data.

Thereafter, the software maintenance tool places the data in the localinventory (operation 1604). In this operation, the software maintenancetool accepts the downlink and places the data in its inventory. Otherdata associated with the downlink data may be displayed in a userinterface. This user interface may allow a user to sort downlink datainto filtered downlink data using various parameters. These parametersmay include, for example, without limitation, aircraft identification,system identification, application identification, or data type.

Next, the software maintenance tool disconnects from the onboardelectronic distribution system (operation 1606). The softwaremaintenance tool is moved from the aircraft to another location totransfer the downlink data. The software maintenance tool connects tothe network (operation 1608). The software maintenance tool then sendsthe downlink data to the library (operation 1610), with the processterminating thereafter.

FIGS. 17-33 describe a library in a software part managementenvironment. In particular, these figures illustrate one example of animplementation of library 406 in software part management environment400 in FIG. 4.

With reference to FIG. 17, a functional block diagram of a library isdepicted in accordance with an advantageous embodiment. Library 1700 isa more detailed example of library 406 in FIG. 4. Library 1700 includesuser interface system 1702 and backend 1704. Backend 1704 includesinterfaces 1706, storage 1708, and management components 1710.

Interfaces 1706 include messaging service 1712, hypertext transportprotocol (HTTP) service 1714, and web service 1716. Storage 1708contains file system 1718 and database 1720. In these examples,management components 1710 include parts vault 1722, command dispatcher1724, command queue manager 1726, system configurator 1728, importedfiles aggregator 1730, report manager 1732, event logger 1734, andsecurity manager 1736.

User interface system 1702 provides an operator access to backend 1704to perform different tasks and operations. User interface system 1702may be a graphical user interface. More specifically, user interfacesystem 1702 may be a web-based application that allows a user to accesslibrary 1700 from a remote location.

Interfaces 1706 contain a number of different interfaces that may beused to transfer information into and out of library 1700. Withininterfaces 1706, messaging service 1712 allows various components withinmanagement components 1710 to communicate with other applications. Inthese examples, report manager 1732 uses messaging service 1712 todistribute reports in response to requests. Messaging service 1712 maybe Implemented using various types of messaging services. For example,messaging service 1712 may be implemented using Java® Messaging Service,which is part of the Java® 2 Enterprise Edition Suite. This product isavailable from Sun Microsystems, Inc.

Web service 1716 may be implemented using any web service system. Webservice 1716 is designed to provide interaction between library 1700 andother devices over a network. Web service 1716 in interfaces 1706 may beimplemented using application programming interfaces accessed over anetwork, such as the Internet. Web service 1716 may be implemented usingvarious protocols such as, for example, simple object access protocol(SOAP) or web surface description language (WSDL). Hypertext transportprotocol (HTTP) service 1714 may be implemented to provide a request andresponse system to manage responses made by clients. These requests aretypically referred to as HTTP requests.

In these examples, hypertext transport protocol service 1714 may be usedto send and receive information, such as files. These files may be, forexample, files containing aircraft software parts, commands, downlinkdata, and other suitable information. In these examples, hypertexttransport protocol service 1714 is used by parts vault 1722, commanddispatcher 1724, imported files aggregator 1730, report manager 1732,and event logger 1734.

As depicted, the different components from components within managementcomponents 1710 may access storage 1708 for various reasons. Storage1708 contains the different storage systems used to store informationwithin backend 1704 of library 1700, such as file system 1718 anddatabase 1720. Storage 1708 is a functional component that storesinformation and may be located on one or more storage devices, such as ahard drive or a random access memory. Storage 1708 may be, for example,located on a single storage device, such as a hard drive.

In other embodiments, storage 1708 may be located on multiple storagedevices, which may be located in the same physical location or indifferent physical locations. Within storage 1708, file system 1718provides a structure or architecture for storing data. This data mayinclude, for example, aircraft software parts, documentation, downlinkdata, and other files. Database 1720, in these examples, may contain,for example, metadata and commands related to files located within filesystem 1718. Additionally, database 1720 may include other commands forperforming other functions such as, for example, deleting files on anaircraft or downloading downlink data.

Parts vault 1722 provides processes to manage the storage anddistribution of aircraft software parts to different aircraft. Inparticular, parts vault 1722 provides for a secure distribution ofparts. These processes may receive new aircraft software parts, as wellas package or crate aircraft software parts for distribution to anaircraft.

Command queue manager 1726 is a component that manages aircraftcommands. Command queue manager 1726 may allow a user or operator,through user interface system 1702, to inspect, reorder, and change thestatus of commands within database 1720. The inspection of commands mayallow a user to see different commands or filter commands based ondifferent criteria.

Command dispatcher 1724 is a component that manages creation anddispatching of commands. This component may allow a user or operator,through user interface system 1702, to create uplink, delete, anddownlink commands. Command dispatcher 1724 also provides validations ofinput parameters when creating these various types of commands. Thiscomponent provides a mechanism to group, crate, and dispatch commandswhen external devices request by various criteria.

In these examples, system configurator 1728 manages the configuration ofdata to support operations performed by command dispatcher 1724. Systemconfigurator 1728 allows a user to define, select, or import informationto define external devices that may be connected to library 1700.Additionally, this component may allow defining of aircraft models,particular aircrafts, and destination systems for the aircraft softwareparts. These destination systems, in these examples, may include linereplaceable units located in the aircraft.

Imported files aggregator 1730 performs concurrent importing of largefiles sent from external devices to library 1700. Report manager 1732allows an operator to define reports that may be generated by library1700. These reports may be ones that include information from the eventlogs that may be aggregated from various sources pertinent to theoperation of the software part management environment. For example,report manager 1732 may allow a user to define a report that identifiessuccessful uplinking of a specific type of aircraft software part to aspecific model of aircraft being managed within the software partmanagement environment.

Event logger 1734 logs events with respect to the operation of library1700. Additionally, event logger 1734 may aggregate logs from differentdevices connected to library 1700. These events may include, forexample, without limitation, aircraft software parts received fromoutside sources, successful transfers of aircraft software parts toaircrafts, commands generated for uplinking data, commands generated fordownlinking data, and commands generated to delete aircraft softwareparts.

Next, security manager 1736 provides a mechanism to manage access tolibrary 1700 by operators using user interface system 1702. Securitymanager 1736 may be implemented using roles and responsibilities thatmay be configured for particular users. This type of access may provideusers privileges to access different features or functionalities withinlibrary 1700. Further, security manager 1736 also may provide for securecommunications between external devices and library 1700. As an example,security manager 1736 may ensure that communications through interfaces1706 occur through mechanisms, such as encryption or virtual privatenetworks.

In operation, library 1700 may receive aircraft software parts from anexternal program such as, for example, crate tool 402 in FIG. 4. In thistype of operation, the external program connects a service, such ashypertext transport protocol service 1714 and interfaces 1706. Securitymanager 1736 performs authentication of the connection and determineswhether aircraft software parts can be imported. If the connection isallowed, hypertext transport protocol service 1714 may then send arequest to parts vault 1722 to handle the input process. In thisprocess, parts vault 1722 writes metadata about the aircraft softwareparts into database 1720 while storing the actual aircraft softwareparts within file system 1718 in some selected file directory.

When managing parts in library 1700, aircraft software parts may beretrieved from file system 1718 through parts vault 1722 and sent to auser for inspection or review. Further, aircraft software parts may bearchived in file system 1718. This type of archiving saves the part insome designated directory or other storage device. Further, parts vault1722 also may scan certificates for parts within file system 1718 toidentify whether any certificates signing the part have expired. Anotification of expiration may be generated in advance through userinterface system 1702. Further, expiration of a certificate also causesparts vault 1722 to disable any commands that contain the part.

Library 1700 also may be used to create and distribute commands tooutside devices. These commands may be created by an operator throughuser interface system 1702. User interface system 1702 allows a user toenter information for commands. Once the commands are generated, thesecommands are stored within database 1720.

When these commands are needed by external devices, the commands may becrated and sent via interfaces 1706. In particular, web service 1716 maybe used to send these commands to an outside component, such as a proxyserver application or software maintenance tool. If aircraft softwareparts are specified by a command, these parts may be sent in a separatetransfer through hypertext transport protocol service 1714 in theseexamples. These aircraft software parts may be sent when requested orsent as part of the transfer, depending on the particularimplementation.

Additionally, reports are examples of other data that may be stored infile system 1718. These reports may be, for example, spreadsheets, partslists, and live reports.

Information obtained from downlinking data, such as files and devicelogs, may be stored within file system 1718. These files may beaggregated using imported files aggregator 1730. This component mayaccept files and create metadata entries in database 1720, in additionto saving the files within file system 1718.

The different components illustrated for library 1700 are presented asone example of communication for different functions. The presentationand organization of these different components is not intended to implyarchitectural limitations to the manner in which the components may beimplemented. For example, the different components within library 1700may be subdivided or combined in other fashions other than that asdisplayed. Additionally, in other implementations, some functions may beomitted or other functions may be added. Further, some functions may becombined and implemented as a single module or application withinlibrary 1700. As another example, interfaces 1706 may be implementedusing other interfaces in addition to, or in place of, the onesillustrated.

Turning now to FIG. 18, a diagram illustrating a file system directorylayout is depicted in accordance with an advantageous embodiment. Filesystem directory layout 1800 is an example of a layout or schema usedwithin file system 1718 in FIG. 17. In this example, file systemdirectory layout 1800 defines information used to locate files withinfile system 1718 in FIG. 17. The file types include, for example,downlink 1802, log 1804, part 1806, alternate part sign list (APSL)1808, spreadsheet 1810, and archive 1812.

Each of these types of files is identified within file system directorylayout 1800 with different types of information. For example, downlink1802 includes date 1814, device 1816, tail number 1818, uniqueidentifier (UID) 1820, and downlink file name 1822. Date 1814 identifiesthe creation date of the downlink file. Device 1816 identifies thedevice that transferred the downlink data from the aircraft to thelibrary. This device may be, for example, a proxy server application orsoftware maintenance tool. Tail number 1818 identifies a particularaircraft on which the downlink data was located. Unique identifier 1820uniquely identifies the file within the file system. Downlink file name1822 is the name of the downlink file.

Next, log 1804 includes device 1824, unique identifier (UID) 1826, andeventlog filename 1828. Part 1806 is for an aircraft software part andincludes unique identifier (UID) 1830, crated 1832, crate file name1834, and crated part file name 1836. Crated 1832 identifies a directoryin which the crate, containing the aircraft software part, is located.Crate file name 1834 is a name of the crate file. Crated part file name1836 is the name of the file containing the aircraft software part.

Alternate part signature list 1808 includes unique name 1838, andspreadsheet 1810 includes unique name 1840. Archive 1812 includesaircraft software part (SAP) 1842, unique identifier (UID) 1844, andcrate file name 1846.

File system directory layout 1800 is provided as an example of oneimplementation for file system 1718 in FIG. 17. In other advantageousembodiments, other file system layouts or schemas may be used, which aresuitable for the particular implementation.

With reference now to FIG. 19, a block diagram illustrating anorganization of commands in queues is depicted in accordance with anadvantageous embodiment. In this example, queues 1900, 1902, and 1904are examples of queues that are located in database 1720 in FIG. 17.

Queue 1900 includes commands 1906; queue 1902 includes commands 1908;and queue 1904 includes commands 1910. Commands 1906, 1908, and 1910 arecommands destined for a particular aircraft in these examples. Thecommands may be, for example, uplink commands, downlink commands, ordelete commands. An uplink command is a command that sends informationfrom library 1700 in FIG. 17 to an aircraft, while a downlink command isa command that sends information from an aircraft to library 1700 inFIG. 17.

A delete command is a command that is used to delete information on theaircraft. This information may be, for example, an aircraft softwarepart, a configuration file, or a manual. Each of these queues, in theseexamples, is associated with a particular ground tool or device. Inthese examples, queues 1900, 1902, and 1904 are associated or designatedfor different devices that are to distribute the commands to aircraft.

For example, queue 1900 may be associated with a first proxy serverapplication, queue 1902 with a second proxy server application, andqueue 1904 with a software maintenance tool. When different devicescontact library 1700 in FIG. 17, commands are distributed to thosedevices based on whether commands are present in the queues associatedwith those devices.

Turning now to FIG. 20, a block diagram of an aircraft software part isdepicted in accordance with an advantageous embodiment. In this example,aircraft software part 2000 is stored in crate 2002. Crate 2002 isstored within file system 1718 in FIG. 17.

Crate 2002 is a file in these examples. Crate 2002 may be, for example,without limitation, in a zip file format. Crate 2002 also may, in someembodiments, contain more than one aircraft software part. Aircraftsoftware part 2000 may include a set of files that provide functionalityfor the particular part. These files may include, for example,executable files, data files, configuration files, and library files.

In the depicted embodiments, crate 2002 and aircraft software part 2000are signed. In other words, aircraft software part 2000 is signed withone digital signature, while crate 2002 is signed with another digitalsignature. These digital signatures may be the same or different,depending on the particular embodiment. Of course, in otherimplementations, aircraft software part 2000 may not be stored in crate2002.

With reference now to FIGS. 21-23, examples of command data structuresare depicted in accordance with an advantageous embodiment. Thedifferent command data structures illustrated in these figures areexamples of temporary data structures created from commands stored inqueues, such as queues 1900, 1902, and 1904 in FIG. 19.

Turning now to FIG. 21, a command data structure for a delete command isdepicted in accordance with an advantageous embodiment. In this example,delete command data structure 2100 includes parameters 2102, 2104, 2106,2108, 2110, and 2112.

Parameter 2102 identifies a set of file names to be deleted. Parameter2104 identifies a set of part identifiers to be deleted. Parameter 2106is a set of airplane identifiers that identify the particular aircraftto receive the delete command. This list of airplane identifiers may be,for example, tail numbers. Parameter 2108 identifies a set of devicesthat are to send the command. These devices may be, for example, groundtools, such as a proxy server application or software maintenance tool.

Parameter 2110 identifies the destination system to receive the command.In these examples, the destination system is the particular linereplaceable unit that is to receive the command. Parameter 2112identifies a user that requests the command.

In FIG. 22, a diagram illustrating a command data structure for anuplink command is depicted in accordance with an advantageousembodiment. In this example, uplink command data structure 2200 includesparameters 2202, 2204, 2206, 2208, and 2210. Parameter 2202 identifiesthe aircraft software part to be uplinked or sent. Parameter 2204identifies a set of airplanes to receive the commands. These parameterscontain aircraft identifiers. Parameter 2206 is a set of deviceidentifiers for devices to process the command. Parameter 2208 is a setof parameters identifying the destination system to receive the command.Parameter 2210 identifies the user that requested the command.

Turning next to FIG. 23, a diagram illustrating a data structure for adownlink command is depicted in accordance with an advantageousembodiment. In this example, downlink command data structure 2300includes parameters 2302, 2304, 2306, 2308, and 2310.

Parameter 2302 identifies the type of data that is being downlinked.Parameter 2304 identifies a set of aircraft to receive the command todownlink data. Parameter 2306 is for a set of devices to send thecommand to the set of aircraft. Parameter 2308 identifies a set of linereplaceable units on the set of aircraft to receive the command.Parameter 2310 identifies a user that requests the command.

These command data structures are abbreviated forms of the commands thatallow devices, such as a proxy server application or softwaremaintenance tool, to begin processing the commands referenced by thecommand data structures. These command data structures may reduce theamount of traffic across various communications links in these examples.The devices may request the actual commands after receiving thesecommand data structures. These command data structures are deleted afterbeing sent to the ground tools in these examples.

With reference now to FIG. 24, a diagram of a user interface fordispatching commands is depicted in accordance with an advantageousembodiment. Window 2400 is an example of a user interface that may bepresented through user interface system 1702 for command dispatcher 1724in FIG. 17.

In this example, a user may select between creating commands, such asuplink commands and downlink commands. This selection may be madethrough controls 2402 and 2404. Control 2402 may be used to generate anuplink command, while control 2404 may be used to generate a downlinkcommand. Control 2406 may be used to generate delete commands.

In this depicted example, control 2402 has been selected, resulting insection 2408 being displayed within window 2400. Section 2408 provides auser an ability to input information to create an uplink command. Forexample, the user may select an airplane tail number from list 2410.These airplane tail numbers are unique to particular aircraft.

The user also may select a device in the form of a proxy serverapplication from list 2412 to distribute the command. Also, devices inthe form of software maintenance tools may be selected through list2414. The destination system on the aircraft may be selected throughfield 2416. The destination system is a particular line replaceable unitin these examples. Field 2418 allows the entry of a part number. Entryof this part number provides other information about the part shown infields 2420, 2422, 2424, 2426, and 2428. The particular informationdisplayed about the part may vary, depending on the particularimplementation.

Field 2416 has different selectable values for different command types.

FIGS. 25-26 are diagrams of graphical user interfaces in accordance withan advantageous embodiment. These graphical user interfaces are examplesof interfaces that may be presented through user interface system 1702in FIG. 17. These depicted graphical user interfaces are presented forpurposes of illustrating one particular implementation and not meant tolimit the manner in which a graphical user interface may be designed orpresented by user interface system 1702 in FIG. 17.

Turning to FIG. 25, a diagram illustrating a user interface for viewingcommands is depicted in accordance with an advantageous embodiment. Inthis example, window 2500 is an example of a graphical user interfacethat may be displayed through user interface system 1702 for commandqueue manager 1726 in FIG. 17. In this example, the user may view thestatus of various commands. In particular, specific types of commandsmay be viewed through window 2500.

Commands may be viewed using controls 2502, 2504, and 2506. Pendingcommands may be viewed by selecting control 2502, executed commands maybe viewed by selecting control 2504, and dequeued commands may be viewedby selecting control 2506. A user may reorder or change the order inwhich commands are stored in the queue through control 2508. In thisexample, pending commands have been selected and are displayed withinsection 2510 of window 2500.

With reference now to FIG. 26, a diagram of a user interface for viewingparts is depicted in accordance with an advantageous embodiment. Window2600 is an example of a graphical user interface presented through userinterface system 1702 for parts vault 1722 in FIG. 17.

In this depicted example, aircraft software parts within the library maybe viewed. Valid parts may be viewed through the selection of control2602, incoming parts may be viewed through the selection of control2604, expired parts may be viewed through the selection of control 2606,and faulty parts may be viewed through the selection of control 2608. Inthis example, control 2602 has been selected, and valid parts locatedwithin the library are displayed within section 2610 of window 2600.

With reference now to FIG. 27, a flowchart of a process for receivingaircraft software parts in a library is depicted in accordance with anadvantageous embodiment. The process illustrated in FIG. 27 may beimplemented in library 1700 in FIG. 17. In particular, these processesmay be implemented in parts vault 1722 within management components 1710of library 1700 in FIG. 17.

The process begins by receiving an aircraft software part (operation2700). In receiving the aircraft software part, metadata is received aswell as a stream of data for the aircraft software part. The processdetermines whether the metadata for the aircraft software part iscorrect (operation 2702). In these examples, the metadata is data thatis associated with and/or describes the aircraft software part.

In these examples, the following metadata may be checked: whether partname conforms to the regular expression [̂˜/:*?\″< >,|.\\]* and less orequal to 200 characters; whether the production status is BLACK_LABEL ,RED_LABEL, or BLUE_LABEL; whether the applicable standard is of a lengthgreater or equal to 0 and less or equal to 500 characters; whether theintellectual property owner is of a length greater or equal to 0 andless or equal to 100 characters; whether the release date has a correctdate format; and whether the description is of a length greater or equalto 0 and less or equal to 2000 characters.

If the metadata for the part is correct, the process registers atemporary entry in the database in the library (operation 2704). Thistemporary entry is used to provide a status of the process for receivingthe part. The entry initially indicates that the receiving of the parthas begun. The process also creates a directory structure in the filesystem (operation 2706). This directory structure is used to saveportions or fragments of the file containing the aircraft software partas the file is received.

A determination is made as to whether the receipt of the aircraftsoftware part is complete (operation 2708). If the receipt of theaircraft software part is not complete, the progress is updated in thedatabase (operation 2710), and the file fragments received are saved inthe file system (operation 2712). This progress may be displayed in theuser interface. The process then returns to operation 2708 to continuechecking the status of the received operation for the aircraft softwarepart.

When the receipt of the aircraft software part is complete in operation2708, the process determines whether the part is integral (operation2714). This operation is performed to determine whether the aircraftsoftware part is complete and whether the part has errors. The check maybe made by matching a certificate to the received part.

If the aircraft software part is integral, the process crates theaircraft software part (operation 2716). The process then determineswhether the crating operation was successful (operation 2718). If thecrating was successful, the part is marked as complete in the database(operation 2720). The crated part is saved in the file system for laterretrieval (operation 2722), with the process terminating thereafter.

With reference again to operation 2718, if the crating operation is notsuccessful, an error is generated (operation 2724). Thereafter, theprocess removes the entry from the database (operation 2726), andremoves the saved data for the aircraft software part (operation 2728),with the process terminating thereafter. With reference again tooperation 2714, if the aircraft software part is not integral, theprocess also proceeds to operation 2724. Operations 2726 and 2728 areperformed to clean up the database entry and the file system entry forthe failed receipt of the aircraft software part.

With reference again to operation 2702, if the metadata for the aircraftsoftware part is not correct, the process generates an error (operation2730), with the process terminating thereafter. The errors generated inoperations 2730 and 2724 may be stored in a log for later use.

Turning now to FIG. 28, a flowchart of a process for creating a commandis depicted in accordance with an advantageous embodiment. The processillustrated in FIG. 28 may be implemented in library 1700 in FIG. 17. Inparticular, this process may be implemented in command dispatcher 1724in FIG. 17.

The process begins by receiving a user request to create a command(operation 2800). This command may be received through a user interface,such as that provided through user interface system 1702 in FIG. 17. Auser may select one of three command types in these examples. Thecommand types include uplink, downlink, and delete. The processidentifies a command type from the user input (operation 2802).

In response to the type of command identified, the process generates alist of parameters and possible values (operation 2804). This listincludes, for example, aircraft tail numbers, applicable device namelists, and destination line replaceable units to receive the command.The process then selectively presents the list and values to the user(operation 2806). In these examples, the list is a context-sensitivelist that provides additional options or values, depending on theprevious selections made by the user.

The process receives user input selecting values from the presented listand values (operation 2808). The process then validates the context ofthe parameters (operation 2810). In these examples, the contextsensitive values exist in user interface system 1702 in FIG. 17. Thisinterface implements what is allowable within a command type the valuesof destination systems. Operation 2810 rechecks these rules at backend1704 in FIG. 17. Backend 1704 may serve other user interfaces other thanuser interface system 1702 in FIG. 17 that may not have the samevalidation rules.

The process creates a set of commands (operation 2812). In operation2812, the process creates a command for each combination of commandtype, tail number, and device name. Of course, other rules and policiesmay be used to identify what commands are created from the userselections. Typically, all commands of the same type and target to thesame aircraft may be logically grouped. Thereafter, the set of commandsis saved in the database in the library (operation 2814), with theprocess terminating thereafter.

With reference to FIG. 29, a high-level flowchart of a process formanaging aircraft software parts is depicted in accordance with anadvantageous embodiment. The process illustrated in FIG. 29 may beimplemented in library 1700 in FIG. 17 in these examples.

The process begins by sending command structures to distribution devices(operation 2900). These command structures may be, for example, deletecommand data structure 2100 in FIG. 21, uplink command data structure2200 in FIG. 22, or downlink command data structure 2300 in FIG. 23.These command structures are sent in response to requests for commandsfrom various devices, such as a proxy server application or softwaremaintenance tool.

Thereafter, command files are sent to the devices (operation 2902).These command files are sent in response to requests for the commandsthemselves when a particular device executes a command. Commandstructures are sent instead of sending command files to reduce theamount of traffic that may occur from constant polling by variousdevices. Instead, command files are sent when devices actually beginexecuting the commands. Thereafter, the process sends the aircraftsoftware parts (operation 2904), with the process terminatingthereafter. In this operation, the aircraft parts are sent as part ofthe execution of a command.

Turning now to FIG. 30, a flowchart of a process for dispatching commandstructures is depicted in accordance with an advantageous embodiment.The process illustrated in FIG. 30 is a more detailed description ofoperation 2900 in FIG. 29.

The process begins by receiving a request from a device (operation3000). In these examples, the device may be, for example, a proxy serverapplication or a software maintenance tool. Of course, the device may beany device that contacts or connects to the library to obtain commands.

The process then queries the database for commands associated or placedin a command queue for the particular device (operation 3002). Operation3002 may be implemented using command queue manager 1726 in FIG. 17. Theprocess receives a result from the query (operation 3004).

Thereafter, the process creates a command data structure containing thecommands for the device (operation 3006). The process then returns thecommand data structure to the device (operation 3008), with the processterminating thereafter. In these examples, the command data structuresare created upon a request by a device for commands. In otherembodiments, the command data structures may be created and broadcast tomany devices based on some event or on a period event, such as theexpiration of a timer.

Turning now to FIG. 31, a flowchart of a process for dispatching commandfiles is depicted in accordance with an advantageous embodiment. Theprocess illustrated in FIG. 31 is a more detailed description ofoperation 2902 in FIG. 29. The process illustrated in FIG. 31 may beimplemented in a component, such as command dispatcher 1724 in FIG. 17.

At this point in the process, the device has received a command datastructure for processing. The device may perform some processing of thecommand based on this command data structure. For example, the devicemay begin to establish a communications link with the aircraft. Thecommand data structure provides sufficient information for the device toperform various processes. The propagation of the command to theaircraft, however, requires additional information in a command file.

The process begins by receiving a request for a command file from adevice (operation 3100). The process queries the database for thecommand identified by the device (operation 3102). This query is madeusing a unique identifier previously sent in the command structure.

The process then receives results from the database (operation 3104).Operation 3102, in these examples, queries the database based on acommand ID and retrieves all the information about the command which isused to create a crated version of the command in extensible markuplanguage. Operation 3104 could be redundant. These results are used tocreate a command file (operation 3106). The process crates the commandfile (operation 3108). Thereafter, the process returns the crate to thedevice (operation 3110), with the process terminating thereafter.

With reference now to FIG. 32, a flowchart of a process for dispatchingparts is depicted in accordance with an advantageous embodiment. Theprocess illustrated in FIG. 32 is a more detailed description ofoperation 2904 in FIG. 29. The process in this example may beimplemented using command dispatcher 1724 in FIG. 17.

The process begins by receiving a request for an aircraft software partfrom a device (operation 3200). The process queries the database for theaircraft software part (operation 3202). The process retrieves thecrated aircraft software part from the file system (operation 3204), andretrieves metadata for the aircraft software part from the database(operation 3206). The process then performs an integrity check on theaircraft software part (operation 3208). The integrity check isperformed to ensure that the aircraft software part has not beencorrupted while being stored. This integrity check may be made usingvarious error checking processes, including hashing.

A determination is made as to whether the aircraft software part isvalid based on the integrity check (operation 3210). If the aircraftsoftware part is valid, the crated aircraft software part is returned tothe device (operation 3212), with the process terminating thereafter. Onthe other hand, if the aircraft software part is not valid, an errormessage is returned (operation 3214), with the process terminatingthereafter.

Turning now to FIG. 33, a flowchart of a process for dequeuing commandsis depicted in accordance with an advantageous embodiment. The processillustrated in FIG. 33 may be performed by command queue manager 1726 inFIG. 17. This process is used to remove commands from the queue in thedatabase after the commands have been processed.

The process begins by receiving notification of a command execution(operation 3300). In this example, the notification is received from thedevice executing the command. The process looks up the command and itsassociated group (operation 3302). This lookup is performed using aunique identifier for the command. Additionally, other commandsassociated with the executed commands are redundant commands that mayhave been sent to different devices for the same aircraft.

The process marks and dequeues the command from the command queue in thedatabase (operation 3304). The process also dequeues all other commandsin the group (operation 3306). This dequeuing of other commands preventsredundant commands being dispatched to different devices in the future.Thereafter, the status is saved (operation 3308), with the processterminating thereafter.

Turning now to FIG. 34, a diagram illustrating data flow in a proxyserver application is depicted in accordance with an advantageousembodiment. Proxy server application 3400 interacts with components suchas library 3402, software management tool 3404, and onboard electronicdistribution system 3406. In these examples, on ground component 3408provides for transfer of information between library 3402 and onboardelectronic distribution system 3406.

Library 3402 may send new commands and aircraft software parts to proxyserver application 3400 (message A1). The results of the processing ofthose commands and parts may be returned to library 3402 by proxy serverapplication 3400 as command status information (message A2).Additionally, proxy server application 3400 also may send downlink andevent log files to library 3402 (message A3).

With respect to transferring information with onboard electronicdistribution system 3406, on ground component 3408 and proxy serverapplication 3400 may send new commands and aircraft software parts toonboard electronic distribution system 3406 (message A4). Command statusinformation may be returned to on ground component 3408 identifying thestatus of commands and parts sent to onboard electronic distributionsystem 3406 (message A5). Additionally, onboard electronic distributionsystem 3406 may send downlink files to on ground component 3408 (messageA6).

Proxy server application 3400 may send new commands and parts tosoftware management tool 3404 (message A7). Software management tool3404 may return command status after the processing of those files(message A8) and send downlink files or event logs (message A9). Inthese examples, software management tool 3404 may communicate withonboard electronic distribution system 3406. Software management tool3404 provides an alternate route for exchanging information with onboardelectronic distribution system 3406. Software management tool 3404 islocated in a portable data processing system, which may be moved from alocation associated with proxy server application 3400 to the aircraftin which onboard electronic distribution system 3406 is located. Thesedetails are described in more detail with respect to the description ofsoftware management tool 3404 below.

Although the different interactions have been described in a particularorder, any of the different messages and interactions may occursimultaneously at any time.

For example, proxy server application 3400 may send commands andaircraft parts to onboard electronic distribution system 3406 at thesame time onboard electronic distribution system 3406 downloads downlinkdata to proxy server 3400. Further, proxy server application 3400 maysimultaneously service multiple aircraft clients, such as softwaremanagement tool 3404 and onboard electronic distribution system 3406.

With reference now to FIG. 35, a diagram illustrating a proxy serverapplication is depicted in accordance with an advantageous embodiment.Proxy server application 3500 is an example implementation of proxyserver application 3400 in FIG. 34. In this example, proxy serverapplication 3500 includes control process 3502, database 3504, filesystem 3506, on ground component interface 3508, software maintenancetool interface 3510, and on ground component 3512. These two interfacesmay be implemented using application programming interface (API) callsin these examples.

Database 3504 contains commands processed by control process 3502. Eachof the records in database 3504 may identify the status of a command.For example, a record may identify whether a command has been processed,as well as the target aircraft and target line replaceable unit on theaircraft. File system 3506 stores aircraft software parts and downlinkdata in these examples.

On ground component 3512 is a software component in proxy serverapplication 3500 that communicates with the onboard electronicdistribution system on the aircraft. On ground component interface 3508has application programming interfaces that provide calls that may beused by control process 3502 to exchange information with on groundcomponent 3512.

On ground component 3512 functions to allow any processes, such ascontrol process 3502 in proxy server application 3500, to communicatewith an onboard electronic distribution system without having to bespecifically designed to communicate with the onboard electronicdistribution system. As a result, control process 3502 may be changed ormodified without having to include protocols used to communicate withthe onboard electronic distribution system. Further, changes to anonboard electronic distribution system may occur without requiringchanges to all of the processes in proxy server application 3500.Instead, modification or changes may be made to on ground component3512.

Software maintenance tool interface 3510 has application programminginterfaces that provide calls that may be used by control process 3502to communicate with a software maintenance tool. The structure andorganization of database 3504 and file system 3506 may be similar tothat used in a library within the aircraft software part maintenanceenvironment.

Turning to FIGS. 36-39, diagrams illustrating data structures used indatabase 3504 in FIG. 35 are depicted in accordance with an advantageousembodiment. Command result database table 3600 illustrates informationand records for command results. Command result database table 3600includes command result identifier 3602, command identifier 3604, groundstatus 3606, aircraft status 3608, date 3610, command type 3612,aircraft identifier 3614, and device name 3616.

Command result identifier 3602 uniquely identifies a specific commandresult record, and command identifier 3604 uniquely identifies aspecific command record. Command identifier 3604 may be found in varioustables to relate data in the tables to a specific command record. Groundstatus 3606 identifies the origination of the command status messages,which may be from an on ground component or an onboard electronicdistribution system in these examples. Aircraft status 3608 is a commandstatus message that can originate from an on ground component or anonboard electronic distribution system. The ground status identifies thestatus of the uplink or downlink of the file being uplinked ordownlinked.

This information provides the percentage completeness of the actualuplink or downlink of the file. Each percentage may be reported as aseparate status. Using an uplink as an example, a status message ofone-quarter done, followed by a one-half done status message, then athree-quarters done message, and finally a done status message would allbe sent as the contents of the file were being sent to the onboardelectronic distribution system. The reporting of each message would bean indication that the appropriate amount of the file contents had beensuccessfully delivered. The same may occur with file contents beingwritten to the ground component during a downlink operation.

Date 3610 identifies the date that the particular device sent thecommand result. Command type 3612 identifies the type of command, suchas uplink, downlink, or delete. Aircraft identifier 3614 is a uniquevalue identifying a specific aircraft within an airline's fleet ofaircraft. Device name 3616 identifies the name of the device sending thecommand result to the proxy server application.

Turning now to FIG. 37, a diagram of a downlink file database table isdepicted in accordance with an advantageous embodiment. In this example,downlink file database table 3700 illustrates information in a downlinkfile database table. Downlink file database table 3700 includes downlinkfile identifier 3702, airplane identifier 3704, device 3706, date 3708,file name 3710, file universal resource locator 3712, and file status3714.

With reference now to FIG. 38, command and command resource databasetables are depicted in accordance with an advantageous embodiment. Inthis example, command database table 3800 represents commands, whilecommand resources database table 3802 represents command resources.Command database table 3800 includes command identifier 3804, airplaneidentifier 3806, application name 3808, command type 3810, device name3812, system name 3814, date 3816, servicing status 3818, priority 3820,command group 3822, crated command 3824, and crated command path 3826.

Command resources database table 3802 includes command resourceidentifier 3828, data type 3830, application standard 3832, partexpiration date 3834, owner 3836, name 3838, production status 3840,release date 3842, supplier 3844, path 3846, crate expiration date 3848,and command identifier 3850. Command resources identified in commandresources database table 3802 are aircraft software parts in crates foruplink commands, file or configuration reports for downlink commands,and files or aircraft software part files for delete commands.

Command identifier 3804 uniquely identifies this specific command resultrecord. Airplane identifier 3806 identifies a particular aircraft.Application name 3808 identifies the line replaceable unit and theaircraft. For example, application name 3808 may identify a particularline replaceable unit. Device name 3812 identifies the different devicesfor which the command is dispatched to an aircraft. The device nameidentifies, for example, a particular proxy server application orsoftware maintenance tool.

In these examples, the name may be a specific name for the particularproxy server application or software maintenance tool. System name 3814identifies the name of the system on which the application is present.Date 3816 identifies the date that the command was created by thecommand dispatcher in the library.

Servicing status 3818 is used to identify the status of a command. Thisfield may identify commands that have been successfully sent to theonboard electronic distribution system and to identify commands that asoftware maintenance tool has reported as being successfully uplinked toan onboard electronic distribution system.

Priority 3820 is a value used to order commands within queues fordistribution to an onboard electronic distribution system. Command group3822 may be used to group commands. Crated command 3824 is the name ofthe file containing the crated format of the command. Crated commandpath 3826 is a path identifying the location of where the crated commandis stored.

In command resources database table 3802, command resource identifier3828 uniquely identifies the command resource record. Data type 3830identifies the type of data for the resource. Application standard 3832identifies a standard applicable to the aircraft software part. Partexpiration date 3834 indicates when the aircraft software part expiresand/or is no longer usable. For example, the data type may be anaircraft software part or a file. Owner 3836 identifies the intellectualproperty owner of the aircraft software part. Name 3838 is the name ofthe file or the aircraft software part in these examples.

Production status 3840 identifies the production status of the aircraftsoftware part within a crate. This status may be, for example, redlabel, blue label, or black label. A red label part is anon-deliverable, production quality hardware or software part underengineering development. A blue label part is controlled and maintainedand is restricted for use in a laboratory environment only. A blacklabel part is considered production ready and can be delivered to anairline customer.

Release date 3842 identifies the date that the aircraft software part inthe crate was released. Supplier 3844 identifies the supplier of theaircraft software part. Path 3846, in these examples, identifies thelocation of the aircraft software part. For example, a universalresource locator string may be used for retrieving the part. Crateexpiration date 3848 is the date that the certificate used to sign thecrate expires. Command identifier 3850 identifies the specific aircraftcommand record.

Crated command files may be associated with records in the command tableby storing the file name in the crated command field in combination withthe file path string. Aircraft software part crate files may beassociated to records in the command resource table in command resourcesdatabase table 3802 by storing the file name in name 3838 in combinationwith a file path string.

In FIG. 39, a diagram illustrating an airplane command database table isdepicted in accordance with an advantageous embodiment. In this example,airplane command database table 3900 provides an example of informationfound for airplane commands. Airplane command database table 3900includes airplane command identifier 3902, message identifier 3904,airplane identifier 3906, command type 3908, and command XML 3910.

Airplane command identifier 3902 is used to uniquely identify theparticular aircraft command record. Message identifier 3904 is anidentifier for partial downlinks related to a particular downlinkcommand. This identifier is generated for downlink files that are notthe result of a downlink command sent to the onboard electronicdistribution system. Command XML 3910 identifies the extensible markuplanguage document file format of the particular downlink command thatthe onboard electronic distribution system sent that will be retrievedwhen the onboard electronic distribution system requests a partialdownlink file.

In these examples, the different tables may be related to each otherthrough the command identifier. The different database table definitionsare for different data elements handled by the proxy server application.Different processes may use one or more of these tables to indicate whena record is inserted, updated, or deleted.

Turning now to FIG. 40, a diagram of a proxy server file systemdirectory structure is depicted in accordance with an advantageousembodiment. In this example, directory structure 4000 represents a filesystem directory structure. Directory structure 4000 is an example ofone type of directory structure that may be implemented in file system3506 in FIG. 35. Directory structure 4000 may identify different typesof files stored within a file system on a proxy server application.

In these examples, directory structure 4000 includes crated commands4002, crate 4004, downlink files 4006, downlink files archive 4008,downlink files partial 4010, archived event file logs 4012, event log4014, and temporary files 4016. This type of directory structure is usedto store files in the file system, as well as to identify or locatefiles within the file system in these illustrative examples.

Turning now to FIG. 41, a flowchart of a process for receivinginformation from a library is depicted in accordance with anadvantageous embodiment. In this example, the process illustrated inFIG. 41 may be implemented in control process 3502 in FIG. 35. Thisprocess is used to receive commands and parts from a library in theaircraft software part maintenance environment. This process may beinitiated in response to an event. For example, the event may be theexpiration of a timer. In other embodiments, the event may be caused byother sources. For example, the event may be initiated by a user input.

The process begins by identifying successfully executed commands(operation 4100). These commands are ones that the proxy serverapplication sent to a set of aircraft in which the processing of thecommands occurred successfully. The commands may be, for example, todelete a software aircraft file, load a software aircraft file, ordownlink data from a line replaceable unit on the aircraft.

These commands may be identified from a database within the proxy serverapplication, such as database 3504 in FIG. 35. The particular commandsmay be identified from command identifiers in a command result databasetable, such as command result database table 3600 in FIG. 36. Theidentification of these commands forms a list of commands that is sentto the library (operation 4102). Operations 4100 and 4102 are used tosend command status information to the library.

Next, the process requests a command list from the library (operation4104). Operation 4104 is performed to initiate processing of newcommands for distribution to a set of aircraft. The process receives aresponse from the request (operation 4106). A determination is made asto whether a command list is received in the response (operation 4108).If a command list is not received, the process terminates with no newcommand present to process. Otherwise, the process deletes commandsstored within the database that are not found on the new command listreceived from the library (operation 4110).

In operation 4110, the commands that are present in the database withthe proxy server application that are not included in the list ofcommands retrieved from the library are considered to be unnecessary forthe proxy server application to process or handle. This feature makesthe library the authoritative source for commands that are supposed tobe processed and found on different proxy server applications in theseexamples.

If the proxy server application receives a command and the command iscanceled by a user before processing, the command dispatcher in thelibrary deletes the command for the device. As a result, the proxyserver application will not receive the command in the list of commandsduring a future cycle in which commands are requested. In this manner, auser may remove all the commands for a particular proxy serverapplication by deleting pending commands for that proxy serverapplication from a command queue screen.

Thereafter, the process stores new commands in the database (operation4112). In these examples, the command list may be in the form of acommand data structure. The proxy server application will selectivelyrequest the actual commands themselves either immediately or at someother point in time.

The process then selects an unprocessed new command for the process(operation 4114). The process requests a crate containing the command(operation 4116). In response to the request, the process receives thecrate (operation 4118). The received crate is then stored in the filesystem (operation 4120). The process then determines whether anyunprocessed new commands are still present (operation 4122). Ifadditional unprocessed new commands are present, the process returns tooperation 4114 to select another unprocessed new command for processing.

Otherwise, in operation 4122, the process determines whether uplinkcommands are present in the new commands received (operation 4124). Ifuplink commands are present, an unprocessed uplink command is selectedfor processing (operation 4126). The process then determines whether acrate containing an aircraft software part is already present in thefile system (operation 4128). If a crate is present, the process returnsto operation 4124 as described above.

If a crate is not present, the process requests the crate containing theaircraft software part corresponding to the command from the library(operation 4130). Thereafter, the process receives the crate (operation4132) and stores the crate in the file system (operation 4134).

The process then returns to operation 4124 to determine whetheradditional unprocessed uplink commands are present. If additionalunprocessed uplink commands are not present, the process terminates.Otherwise, the process returns to operation 4126 to select anotherunprocessed uplink command as described above.

During execution of the process in FIG. 41, three types of event logmessages are created and recorded. A record indicating that the proxyserver application successfully connected to the library is one eventrecorded in the log. An event indicating that a list of receivedcommands has been received from the library is another event that isrecorded. An event is also recorded for each command that is placed intoa queue for an aircraft identified by the command. The list ofsuccessful commands sent to the library may be used in aiding an airlinewith planning maintenance operations.

Turning now to FIG. 42, a flowchart of a process for sending downlinkfiles to a library is depicted in accordance with an advantageousembodiment. The process illustrated in FIG. 42 may be implemented in acontrol process, such as control process 3502 in FIG. 35. This processillustrates the different operations that occur when a proxy serverapplication sends a downlink file received from an onboard electronicdistribution system to a library. This process may be initiated by anevent, such as a timer. This process may be initiated at a differenttime from the process for handling commands that is illustrated in FIG.41 to help spread out a traffic network and reduce congestion.

The process begins by identifying downlink records for untransferreddownlink data in the database (operation 4200). A determination is madeas to whether unprocessed records are present in the database (operation4202). If unprocessed records are present, an unprocessed record for adownlink file is selected for processing (operation 4204). The processsends the file containing the downlink data to the library (operation4206).

Thereafter, the process archives the file sent to the library (operation4208). The process then updates the database record for the file asbeing archived (operation 4210). A determination is then made as towhether additional unprocessed records are present (operation 4212). Ifadditional unprocessed records are present, the process returns tooperation 4204.

Otherwise, the process identifies records in the database that are olderthan some selected threshold (operation 4214). This threshold may be,for example, some selected number of hours since the date and/or time inthe timestamp indicating when the downlink file was received. Theprocess deletes any identified records from the database (operation4216), with the process terminating thereafter. With reference again tooperation 4202, if unprocessed records are not present, the process alsoterminates.

Turning now to FIG. 43, a flowchart of a process for sending event filesto a library is depicted in accordance with an advantageous embodiment.The process illustrated in FIG. 43 may be implemented in a proxy serverapplication component, such as control process 3502 in FIG. 35. As withthe other processes, the process illustrated in FIG. 43 may be initiatedin response to an event, such as a timer.

The process in this figure supports sending event logs back to thelibrary for analysis for use in planning operations, such as maintenanceoperations. The event log sent to the library in FIG. 43 captures eventmessages that are the result of user interaction with an applicationuser interface system and/or interface interaction between applicationcomponents. This type of information may be used during businessprocesses of an airline for reporting during an audit to ensure thatvarious processes are followed for specific operations.

The process begins by comparing a current log file with a copy of thelog file from a previous processing cycle (operation 4300). The processidentifies any new events that have occurred from the comparison of thetwo log files (operation 4302). The process then sends events for newentries found in comparison to the library (operation 4304). A copy ofthe files sent to the file system is archived (operation 4306). Theprocess then sends any rollover log files to the library (operation4308). Rollover log files are files present from a previous period oftime, such as a previous date.

The process archives a copy of any file in the file system sent to thelibrary (operation 4310). The process then deletes the rollover logfiles sent to the library (operation 4312). Next, the previous copy ofthe log file is deleted and the current log file is set as the copy foruse in the next comparison (operation 4312). The process then looks fordevice name subdirectories within the event logs direction (operation4314). In operation 4314, subdirectories with a device name are createdwhen a proxy server application writes event log files for receivedfiles from a software maintenance tool into the file system.

The process looks for event log files in any found subdirectories(operation 4316). Afterwards, the process sends any event log filesfound in the subdirectories to the library (operation 4316). The processthen deletes all of the sent files and empties the subdirectories(operation 4318). The process then terminates.

Turning now to FIG. 44, a flowchart of a process for sending informationto an aircraft is depicted in accordance with an advantageousembodiment. In these examples, the process illustrated in FIG. 44 may beimplemented in a software component, such as control process 3502 withinproxy server application 3500 in FIG. 35. In these examples, theinformation takes the form of commands and aircraft software parts sentto an onboard electronic distribution system on the aircraft.

The process begins by receiving a request for a next command from theonboard electronic distribution system (operation 4400). Thereafter, theprocess obtains the next command requested by the onboard electronicdistribution system (operation 4402). In these examples, the actual filefor the command is located in the file system of the proxy serverapplication. The record in the database contains the metadata about thecommand in the file system.

The process then updates the database record for the command to indicatethat the command has been serviced (operation 4404). The process makes adetermination as to whether the next command is a delete command(operation 4406). If the next command to be processed is not a deletecommand, the process then makes a determination as to whether theaircraft is currently uplinking information (operation 4408).

If the aircraft is currently uplinking information, the processdetermines whether the aircraft is also downlinking information(operation 4410). If the process is not downlinking information, adetermination is made as to whether the next command is an uplinkcommand (operation 4412). If the next command is not an uplink command,the process finds the next command and returns that command to theonboard electronic distribution system (operation 4414), with theprocess terminating thereafter.

With reference again to step 4406, if the next command to be processedis a delete command, the process proceeds to step 4414 as describedabove. With reference again to operation 4412, if the next command is anuplink command, the process finds and returns the next downlink commandor delete command for the aircraft (operation 4418), with the processterminating thereafter. With reference again to operation 4410, if theaircraft is downlinking, the process finds and returns the next deletecommand in the queue for the aircraft (operation 4416), with the processterminating thereafter.

With reference back to operation 4408, if the aircraft is not uplinking,a determination is made as to whether the aircraft is downlinking(operation 4420). If the aircraft is not downlinking in operation 4420,the process finds and returns the next command for the aircraft(operation 4422), with the process terminating thereafter. If theaircraft is downlinking in operation 4420, a determination is made as towhether the next command for the aircraft is a downlink command(operation 4424).

If the next command is not a downlink command, the process proceeds tooperation 4422 as described above. Otherwise, the process finds andreturns the next uplink command or delete command (operation 4426), withthe process terminating thereafter.

In these examples, the different decisions in determining which commandto send to the aircraft is performed to avoid sending too many uplinkand/or downlink commands to the same aircraft at the same time. Thistype of processing is employed to improve or optimize the use ofbandwidth while the aircraft is communicating with the proxy serverapplication. An event log message is written to a log file during thisprocess that reports when the aircraft software part was uplinked to anaircraft. In other advantageous embodiments, other types of decisionsmay be used to implement other policies that may be desired. Forexample, certain types of commands may be given preference over othertypes of commands. Selected types of aircraft may be given priority overothers.

With reference next to FIG. 45, a flowchart of a process for receivingaircraft software parts is depicted in accordance with an advantageousembodiment. The process illustrated in FIG. 45 may be implemented in asoftware component, such as control process 3502 in FIG. 35. The processillustrated in this example is used to obtain aircraft software partsfrom a proxy server application.

The process begins by receiving a request for a crate containing anaircraft software part from an onboard electronic distribution system(operation 4500). The process locates the crate corresponding to therequest (operation 4502). The process then returns the crate to theonboard electronic distribution system (operation 4504), with theprocess terminating thereafter.

Turning now to FIG. 46, a flowchart of a process for receiving commandstatus information from an aircraft is depicted in accordance with anadvantageous embodiment. The process illustrated in FIG. 46 may beimplemented in a software component, such as control process 3502 inFIG. 35. This process is used to receive status information from anonboard electronic distribution system on an aircraft.

The process in FIG. 46 is employed to obtain status informationregarding the processing of commands on an aircraft. The statusinformation may indicate whether the sending of the command wassuccessful with respect to the particular line replaceable unit.

Further, with uplink commands, the status also will indicate whether theaircraft software part is stored on the aircraft and ready forinstallation. In these examples, the installation of the aircraftsoftware part on the line replaceable unit is one initiated by amechanic or technician. In other embodiments, this type of installationmay be automatic.

The process begins by receiving a call from the onboard electronicdistribution system with a command status (operation 4600). The processinserts a new record in the command results database table with theinformation from the command status (operation 4602), with the processterminating thereafter.

With this information, the proxy server application may send the statusinformation back to the library as to whether the command wassuccessful. This information allows an identification of when aircraftsoftware parts are present on an aircraft and ready for installation ona line replaceable unit. In these examples, three event log messages arecreated. A message indicates whether the specific command wassuccessful. Messages also are sent back indicating which deleted fileswithin a command were successfully deleted. Additionally, theidentification of commands that failed also is logged in the statusmessages.

Turning now to FIG. 47, a flowchart of a process for receiving downlinkfiles is depicted in accordance with an advantageous embodiment. Theprocess illustrated in FIG. 47 may be implemented in a softwarecomponent, such as control process 3502 in FIG. 35. This flowchartillustrates the processes that occur when a downlink file is sent to aproxy server application from an onboard electronic distribution system.

The process begins by receiving a call from the onboard electronicdistribution system to download downlink data (operation 4700). In theseexamples, the on ground component identifies a partial downlink when afile writing operation was previously interrupted and the entirecontents of the file were not written into the file. If the file writingoperation completed successfully, the downlink is a completed downlink.If the call is to send additional data for the downlink, then theinformation received is added onto the file previously stored for thedownlink on the file system with the proxy server application.

The process then receives data for the downlink file (operation 4702).Next, the process determines whether the data is for a partiallydownloaded downlink file (operation 4704). If the data is for a newdownlink file, the process creates a downlink file (operation 4706).Thereafter, the data is stored in the downlink file (operation 4708). Adetermination is then made as to whether additional data is received forthe downlink file (operation 4710). If additional data is received, theprocess returns to operation 4708. Otherwise, the process determineswhether the file is complete (operation 4712). If the file is complete,the file is stored in the file system on the proxy server (operation4714), with the process terminating thereafter.

With reference again to operation 4712, if the file is not complete, theprocess marks the file as a partially downloaded downlink file(operation 4716), with the process terminating thereafter. Withreference again to operation 4704, if the data to be downloaded is for apartially downloaded downlink file, the process determines whether apartial downlink file is present for the data (operation 4718).

If the downlink file is present, the process proceeds to operation 4708as described above. Otherwise, the process sends an error to the onboardelectronic distribution system (operation 4720), with the processterminating thereafter. This area indicates that a partial downlink filefor the data to be sent by the onboard electronic distribution system isnot present on the proxy server. In this situation, the onboardelectronic distribution system may resend the entire file in anotherdata transfer.

In these examples, the onboard electronic distribution system may senddownlink files to the proxy server application at the same time that theonboard electronic distribution system is receiving commands from theproxy server application. This process takes into account thatinterruptions may occur during the downlinking of data to the proxyserver application. If the sending of downlink data is interrupted, thesuccessful written part is saved for later when the rest of the data canbe written. In this manner, rewriting of earlier data is not necessary.In these examples, an event log message may be recorded that indicatesthat the downlink data was received from the proxy server applicationfrom a specific aircraft.

With reference now to FIG. 48, a flowchart of a process for receivingstatus information from a software maintenance tool is depicted inaccordance with an advantageous embodiment. The process illustrated inFIG. 48 may be implemented in control process 3502 in FIG. 35. Thisprocess illustrates the different operations that occur in receivingstatus messages from a software maintenance tool.

The process begins by receiving a call from a software maintenance toolwith command status information for a command (operation 4800).Thereafter, the process inserts a new record in the command resultsdatabase table for the command identified in the call (operation 4802).The process marks the record as software maintenance tool reportedsuccess (operation 4804).

The process returns a confirmation to the software maintenance tool(operation 4806). These different messages may be collected with othermessages to transfer back to the library. The process then marks thelocal copy of the command as sent to the aircraft (operation 4808), withthe process terminating thereafter. This process prevents the proxyserver application from resending the command back to the softwaremaintenance tool.

Turning now to FIG. 49, a flowchart of a process for sending informationto a software maintenance tool is depicted in accordance with anadvantageous embodiment. The process illustrated in FIG. 49 may beimplemented in control process 3502 in FIG. 35. The process sendsinformation in the form of uplink commands and aircraft software partsto the software maintenance tool.

The process begins by receiving requests from the software maintenancetool for a list of commands (operation 4900). This operation may be forvarious types of commands. For example, the request may be for anycommands that have been designated for the particular softwaremaintenance tool. The request may obtain commands for a particularaircraft, a particular line replaceable unit on the aircraft, or someidentifier.

In response to receiving this request, the process locates commandscorresponding to the request in the database (operation 4902). Theprocess then receives a result from the database (operation 4904). Theprocess sends the results back to the software maintenance tool(operation 4906), with the process terminating thereafter. The softwaremaintenance tool may request the crates containing the aircraft softwareparts using a process similar to the one illustrated in FIG. 45 forsending aircraft software parts to an onboard electronic distributionsystem.

Turning now to FIG. 50, a flowchart of a process for sending lists ofaircraft software parts to a software maintenance tool is depicted inaccordance with an advantageous embodiment. This process may beimplemented in a software component, such as control process 3502 inFIG. 35. This process may be used to identify what aircraft softwareparts are available on the proxy server application.

The process begins by receiving a request for a list of aircraftsoftware parts from the software maintenance tool (operation 5000). Theprocess then sends a query to the database to identify the aircraftsoftware parts stored in the file system (operation 5002). Results arereceived from the database (operation 5004). The list of aircraftsoftware parts are sent to the software maintenance tool (operation5006), with the process terminating thereafter.

In these examples, the lists returned in operation 5006 may containunique aircraft software part names that are in the inventory of theproxy server application even if the aircraft software part is on theproxy server application only to support a command that was dispatchedspecifically to that proxy server application and not for other devices.

With reference now to FIG. 51, a flowchart of a process for receivingdownlink files from a software maintenance tool is depicted inaccordance with an advantageous embodiment. The process illustrated inthis example may be implemented in a proxy server application component,such as control process 3502 in FIG. 35.

The process begins by receiving a request from a software maintenancetool to downlink a file (operation 5100). In operation 5100, thisrequest may be made as a hypertext transport protocol request. Adetermination is made as to whether a directory is present for theaircraft (operation 5102). If a directory is present, a determination ismade as to whether the file is already present in the directory(operation 5104).

If the file is not present in the directory, the file is written intothe subdirectory for the aircraft (operation 5106). Thereafter, theprocess inserts a new record in a downlink files database table for thedownloaded file (operation 5108), with the process terminatingthereafter.

With reference again to operation 5104, if the file is already presentin the subdirectory, a timestamp is added to the file name (operation5110), with the process then proceeding to operation 5106 as describedabove.

In operation 5110, a timestamp is added to the file name to allow anadditional copy of the same file to be written without overriding orlosing the original file. As a result, the original file name is presentalong with an additional file having a file name that is similar exceptfor the addition of the timestamp. The contents of the files may beidentical in some cases. With reference again to operation 5102, if thedirectory for the aircraft is not present, the process creates asubdirectory for the aircraft (operation 5112). The process thenproceeds to operation 5106 as described above.

In FIG. 52, a flowchart of a process for receiving event log files froma software maintenance tool is depicted in accordance with anadvantageous embodiment. The process illustrated in FIG. 52 may beimplemented in control process 3502 within proxy server application 3500in FIG. 35.

The process begins by receiving a request from a software maintenancetool to downlink an event log file to the proxy server application(operation 5200). The process then determines whether a subdirectory ispresent for the device (operation 5202). In this example, the device isa software maintenance tool. If a subdirectory is present for thedevice, a timestamp is added to the file name of the file received fromthe software maintenance tool (operation 5204). The process then writesthe file into the device name subdirectory (operation 5206), with theprocess terminating thereafter.

With reference again to operation 5202, if a subdirectory is not presentfor the device, the process creates a subdirectory for that device(operation 5208). The process then proceeds to operation 5204 asdescribed above.

Within aircraft software part management apparatus 300 in FIG. 3, thedifferent advantageous embodiments provide a computer implementedmethod, apparatus, and computer program product for managing aircraftsoftware parts. The different advantageous embodiments provide asoftware maintenance tool located on a portable data processing systemthat may be used to establish connection to a source through a groundnetwork. A set of uplink commands may be retrieved from the sourcethrough this connection. A set of aircraft software parts correspondingto the uplink commands are retrieved from the source through theestablished connection to form a set of retrieved aircraft softwareparts. The set of aircraft software parts is stored in the portable dataprocessing system.

This portable data processing system may then be disconnected from theground network and connected to an aircraft network in an aircraft. Anuplink command is issued from the set of uplink commands to the aircraftnetwork through an on ground component located in the portable dataprocessing system. The stored aircraft software part corresponding tothe uplink command may then be sent to the aircraft network through theon ground component.

This software maintenance tool may be utilized in situations in which anaircraft network is unable to establish a connection with a groundnetwork. For example, at some airports, the aircraft network may beincompatible with the particular ground network that is present. Inother examples, a failure or error in the ground network may prevent theaircraft network from communicating with the ground network to receivecommands and aircraft software parts.

Further, the software maintenance tool on the portable data processingsystem also may be employed to receive data from the aircraft. This datamay be, for example, a downlink file.

With reference next to FIG. 53, a diagram illustrating data flow and asoftware maintenance tool is depicted in accordance with an advantageousembodiment. Software maintenance tool 5300 interacts with components,such as library 5302, proxy server application 5304, and onboardelectronic distribution system 5306. These components also are referredto as sources. In these examples, software maintenance tool 5300provides for the transfer of information between library 5302 and/orproxy server application 5304 and onboard electronic distribution system5306.

Library 5302 may be, for example, library 304 in FIG. 3, while proxyserver application 5304 may be proxy server application 306 in FIG. 3.Onboard electronic distribution system 5306 may be, for example, onboardelectronic distribution system 310 in FIG. 3.

Library 5302 sends new commands and parts to software maintenance tool5300 (message E1). The results of processing these commands in parts maybe returned to library 5302 by software maintenance tool 5300 (messageE2). Additionally, software maintenance tool 5300 also may returndownlink and event log files (message E3).

Depending on the particular implementation or use, software maintenancetool 5300 may receive new commands and parts indirectly from library5302 through proxy server application 5304 (message E4). In a similarfashion, software maintenance tool 5300 may return command status(message E5) and downlink and event log files (message E6) to proxyserver application 5304, which in turn sends this information to library5302.

With respect to transferring information with onboard electronicdistribution system 5306, software maintenance tool 5300 may send newcommands and aircraft software parts to onboard electronic distributionsystem 5306 (message E7). Software maintenance tool 5300 may receive acommand status from onboard electronic distribution system 5306 (messageE8). The command status also may include the status of softwaredirectory parts sent to onboard electronic distribution system 5306.Onboard electronic distribution system 5306 may send downlink and eventlog files to software maintenance tool 5300 for transfer to library 5302(message E9).

Examples of these types of transfers are described in more detail below.Further, these steps and interactions may occur in a particular order,and any of the different messages and interactions may occursimultaneously at any time. For example, software maintenance tool 5300may send new commands and aircraft software parts to onboard electronicdistribution system 5306 at the same time software maintenance tool 5300receives downlink files from onboard electronic distribution system5306. In these examples, software maintenance tool 5300 executes on aportable data processing system, such as a laptop computer. Dataprocessing system 200 in FIG. 2 is an example of the data processingsystem that may be used to implement a laptop computer.

Software maintenance tool 5300 may be transported from one location toanother location to distribute aircraft software parts and to downloadinformation, such as download data or files from line replaceable unitson an aircraft. In the different advantageous embodiments, softwaremaintenance tool 5300 establishes a direct connection with onboardelectronic distribution system 5306. In these examples, a directconnection may be a wire connection or a wireless connection. This typeof connection is made without a network connecting the data processingsystem or systems on the aircraft to the data processing system on whichsoftware maintenance tool 5300 is located.

Turning now to FIG. 54, a block diagram of a software maintenance toolis depicted in accordance with an advantageous embodiment. In thisexample, software maintenance tool 5400 includes library service 5402,database 5404, file system 5406, manager 5408, on ground componentinterface 5410, and on ground component 5412.

Library service 5402 provides an interface to communicate with othercomponents within an aircraft software part management apparatus.Library service 5402 provides software maintenance tool 5400 aninterface to communicate with components such as, for example, a libraryand a proxy server application. Database 5404 contains information, suchas metadata about commands in aircraft software parts or parts in filesystem 5406.

Additionally, database 5404 also may contain information about downlinkinformation. This information is stored in the form of tables andrecords within database 5404. Further, database 5404 may store commandsreceived from a proxy server application for execution by an onboardelectronic distribution system on an aircraft data processing system inthe aircraft.

File system 5406 stores files, such as commands, aircraft softwareparts, and downlink files. The different files may be stored withincrates in file system 5406, depending upon the particularimplementation. Manager 5408 includes processes for managing theoperation of software maintenance tool 5400. In these examples, manager5408 may incorporate processes for presenting user interface views to auser. These views may provide a user an interface to initiate operationsand to view information.

On ground component interface 5410 provides an interface to on groundcomponent 5412. On ground component interface 5410 may be implementedusing application programming interface calls in these examples. Onground component 5412 communicates with the aircraft. In these examples,on ground component 5412 may communicate with an onboard electronicdistribution system located on the aircraft data processing system inthe aircraft. By having an interface to on ground component 5412, onground component 5412 may be changed or modified for particular aircraftor types of aircraft without affecting the other components withinsoftware maintenance tool 5400.

Turning now to FIG. 55, a diagram of commands and command resourcetables is depicted in accordance with an advantageous embodiment. Inthis example, commands table 5500 represents commands, while commandresource table 5502 represents command resources. These tables areexamples of tables that may be found in database 5404 in softwaremaintenance tool 5400 in FIG. 54.

Commands table 5500 includes command identifier 5504, airplaneidentifier 5506, system name 5508, application name 5510, command type5512, priority order 5514, device name 5516, device type 5518, date5520, servicing status 5522, execution status 5524, percent complete5526, execution completion date 5528, and command resource list 5530.Command resource table 5502 includes command identifier 5532, commandresource identifier 5534, data type 5536, crate name 5538, crate path5540, crate file size 5542, production status 5544, application standard5546, owner 5548, supplier 5550, crate expiration date 5552, and releasedate 5554.

The different fields illustrated for commands table 5500 and commandresource table 5502 represent fields that may be found in tables withina software maintenance tool database. In commands table 5500, commandidentifier 5504 uniquely identifies the particular record. Commandidentifier 5504 may be found in various tables to point to a specificcommand record. Airplane identifier 5506 identifies a specific aircraft.In these examples, the identifier may identify an aircraft uniquelywithin a fleet of aircraft for a particular airline. System name 5508identifies the name of the line replaceable unit on which the aircraftsoftware part is located. System name 5508 includes routing informationto identify the line replaceable unit. Data type 5510 identifies theapplication generating the command. Command type 5512 identifies thetype of command. Priority order 5513 indicates whether and what apriority may be for a command file. Device name 5516 identifies aparticular device. Device type 5518 identifies the type of device. Date5520 identifies the date and time that a command was created in thelibrary. Servicing status 5522 identifies commands that have beensuccessfully sent to the onboard electronic distribution system andidentifies commands that have been reported to the library as havingbeen successfully uplinked or executed on the onboard electronicdistribution system.

Execution status 5524 provides a notification of whether the command hasbeen executed on the aircraft. In particular, this command providesinformation as to whether the onboard electronic distribution system onthe aircraft has executed the command. Percent complete 5526 indicatesthe progress of the uplinking of an aircraft software part in a crate bythe onboard electronic distribution system in these examples. Executioncompletion date 5528 identifies when the command execution is complete.Command resource list 5530 identifies a data structure containinginformation about the crate, such as command resource table 5502 in FIG.55.

In command resource table 5502, command identifier 5532 is similar tocommand identifier 5504 in commands table 5500 and provides anidentification of a specific command record. Command resource identifier5534 is used to identify specific command resource records in thedatabase. Data type 5536 identifies the type of data for the resource.For example, the resource may be an aircraft software part or a file. Inthese examples, each command allows different types of information to beassociated with the particular command.

Crate name 5538 identifies the name of the crate in which the aircraftsoftware part is located. Crate path 5540 identifies the location of thecrate containing the aircraft software part. Crate file size 5542identifies the size of the crate. Production status 5544 indicates theproduction status of the particular aircraft software part containedwithin the crate. These values may be, for example, red label, bluelabel, or black label.

Application standard 5546 identifies the applicable standard for theaircraft software part in these examples. Owner 5548 identifies theowner of any intellectual property of the aircraft software partcontained within the crate. Release date 5554 identifies the releasedate of the aircraft software part.

With reference now to FIG. 56, a diagram of partial downlink data isdepicted in accordance with an advantageous embodiment. In this example,partial downlink table 5600 is an example of a table that may be foundin a database within a software maintenance tool, such as database 5404in FIG. 54. As depicted, partial downlink table 5600 contains messageidentifier 5602, airplane identifier 5604, downlink file 5606, andpartial file XML 5608.

Message identifier 5602 is a command identifier for partial downlinksrelated to a downlink command sent to an onboard electronic distributionsystem. This identifier is generated by the onboard electronicdistribution system on an aircraft for downlink files and is not theresult of the downlink command sent to the onboard electronicdistribution system by the library through a proxy server application orthe software maintenance tool. Airplane identifier 5604 identifies theparticular aircraft within a set of aircraft.

Downlink file 5606 specifies the full directory path to the partiallydownlinked file. When an onboard electronic distribution system requestsa downlink file for which an attempt has already been made to downlinkthe file at a prior time, the software management tool returns the pathto the partially downlinked file.

Partial file XML 5608 contains information about the partiallydownlinked file. This information may be used by the onboard electronicdistribution system to resume downlinking of the downlinked file fromwhere the downlinking was previously interrupted. In this manner, thedownlinking of the file may begin from where it was interrupted to avoidhaving to resend the entire file.

Turning next to FIG. 57, a diagram of a downlinks table is depicted inaccordance with an advantageous embodiment. Downlinks table 5700 is anexample of a table in a database in a software maintenance tool, such asdatabase 5404 in FIG. 54. Downlinks table 5700 stores information abouteach downlinked file sent by an onboard electronic distribution systemin these examples. Downlinks table 5700 includes file name 5702, filepath 5704, airplane identifier 5706, system name 5708, data type 5710,AppName 5711, file size 5712, downlink status 5714, downlink received5716, is sent to library 5718, and downlink sent to library 5720.

File name 5702 identifies the name of the file containing the downlinkinformation. File path 5704, in these examples, identifies the locationof the file containing the downlink information. Airplane identifier5706 identifies the aircraft from which the downlink file was received.This identifier is a unique identifier for a set of aircraft, such asaircraft for a particular airline. This identifier may be a tail partnumber. System name 5708 identifies the name of the line replaceableunit on which the aircraft software part is located. Data type 5710identifies the type of data. In the case of downlink information, thedata is identified as a file. AppName 5711 identifies an application onthe aircraft data processing system that is responsible for obtainingthe aircraft software part.

File size 5712 identifies the size of the file containing the downlinkdata. Downlink status 5714 indicates the status of the downlinkoperation. In these examples, downlink status 5714 shows successfuldownlinks. In some embodiments, partial downlinks may be identified bydownlink status 5714. Library 5718 indicates the time when the file wasdownlinked to the software and maintenance tool. Downlink sent tolibrary 5720 indicates the time when the downlinked file is sent to thelibrary or proxy server application. This information is used todetermine when to delete the downlinked file from the softwaremaintenance tool. Downlinked files may be deleted after a configurableamount of time past the time the downlinked file was sent to ensure thatthe downlinked file was backed up on the library or proxy serverapplication to which the downlinked file was sent.

Turning now to FIG. 58, a diagram of a software maintenance tool filesystem directory structure is depicted in accordance with anadvantageous embodiment. In this example, directory structure 5800represents a file system directory structure that may be used in a filesystem, such as in file system 5406 in FIG. 54. Directory structure 5800identifies different types of files to work within the file system on asoftware maintenance tool. In these examples, directory structure 5800includes parts 5802, downlinks 5804, downlinks unpacked dir 5806, route5808, application 5810, logs 5812, and conf 5814.

Parts 5802 identifies a directory that stores crates received from alibrary, directly from the library or through a proxy serverapplication. In these examples, the crates may include commands and/oraircraft software parts. Further, the crates also may be loaded frommedia, such as a flash memory or hard drive attached to the laptop inwhich the software maintenance tool is located. The crates in thisdirectory may be sent to the onboard electronic distribution system onan aircraft.

Downlinks 5804 are a directory used to store downlink files and partialdownlink files received from an onboard electronic distribution system.In these examples, the downlink files may be organized by the tailnumber of the aircraft from which the files originated. Downlinks 5804may include subdirectories named by the aircraft tail numbers in theseexamples. The downlink files are stored in crated form in theseexamples.

Downlink files that have already been sent to the library are notautomatically deleted from downlinks 5804. Instead, these files may bedeleted after some selected amount of time from when they are sent tothe library or proxy server application.

DownlinksUnpackDir 5806 identifies a directory used by the softwaremaintenance tool to unpack the contents of crates. These crates areunpacked to extract information about a downlink file. The file, inuncrated form, may be stored in a directory within downlinks unpackeddir 5806 using the name of the file.

Route 5808 identifies the directory that contains a SMT-route info.xmlfile. This file contains a list of systems, applications, and commandssorted by each of the applications. The contents of these files are usedby the software maintenance tool and indirectly by the library to ensurethat uplink commands are sent to the appropriate aircraft systems.

App 5810 identifies the directory in which the different processes forthe software maintenance tool are installed. Additionally, logs relatedto the software maintenance tool also may be stored in this directory.These logs include, for example, events that may be recorded during theoperation of the software maintenance tool.

Logs 5812 is a subdirectory within app 5810 and contains the eventlogger.xml file last sent to the library and/or proxy server applicationin these examples. Conf 5814 is a subdirectory within app 5810 andcontains property files to define the operation or behavior of thesoftware maintenance tool as to define the behavior of variouscomponents within the software maintenance tool.

Turning now to FIG. 59, a diagram illustrating interface componentsimplemented in a software maintenance tool is depicted in accordancewith an advantageous embodiment. In this example, user interfacecomponents 5900 are examples of user interface components that may beimplemented in manager 5408 within software maintenance tool 5400 inFIG. 54. User interface components 5900 include connection view 5902,uplink command queue view 5904, uplink local inventory view 5906,downlinked files view 5908, events console view 5910, and retrieve fromlibrary view 5912.

Connection view 5902 is a user interface component that provides an areato display functionality tabs. In these examples, the user interfaceprovides device identification information as well as a dropdown boxallowing a user to select between various components, such as an onboardelectronic distribution system, a library, a proxy server application,or other devices. Further, this interface component also may provide acontrol to connect the software maintenance tool to the particulardevice selected from the dropdown box.

Uplink command queue view 5904 provides an interface to view theprogress of uplinking commands and parts. This view also has a controlto delete commands and aircraft software parts. Uplink local inventoryview 5906 provides a user interface to allow an operator of the softwaremaintenance tool to load or import aircraft software parts from a media.This view allows a user to create uplink commands without beingconnected to a ground network. The user may select aircraft softwareparts for uplinking to specific line replaceable units on specificaircraft. This media may be, for example, a portable media, such as aflash memory, a portable hard drive, a compact disc, or a digitalversatile disc. Downlinked files view 5908 provides a user interface toview downlink files received from the onboard electronic distributionsystem. A user also may use this view to delete downlink files as wellas issue downlink control commands.

Events console view 5910 allows a user to view different events thathave occurred during the execution of various processes of the softwaremaintenance tool. For example, events console view 5910 may present adifferent action that occurred in sending an aircraft software part toan onboard electronic distribution system. These events may include, forexample, connection to the aircraft, sending of the file, andidentification of a successful loading of the file.

Retrieve from library view 5912 is a user interface that may be used toinitiate processes for obtaining commands and aircraft software partsfrom a library or proxy server application. Commands table 5500 in FIG.55 identifies fields that may be found in commands table 5500. This viewalso sends back successfully uplinked commands, downlink files, andevent logs.

With reference next to FIGS. 60-65, example implementations of userinterfaces for user interface components 5900 in FIG. 59 are depicted.With reference first to FIG. 60, window 6000 illustrates a main screenor interface that may be presented in user interface components 5900 inFIG. 59. In particular, window 6000 is an example of connection view5902 in FIG. 59. Window 6000 includes tabs 6002, 6004, 6006, 6008 and6010. These tabs may be selected to present controls and information forvarious functions and processes within a software maintenance tool.

Section 6012 displays information about the software maintenance tool.In this example, section 6012 indicates that the software maintenancetool is connected to an aircraft identified by the tail number. List6014 provides a list of other components to which a software maintenancetool may establish connections. Control 6016 allows a user to initiate aconnection to another component. In these examples, a user may selectvarious components, such as an onboard electronic distribution system, alibrary, or a proxy server application from a set of proxy servers.

With reference now to FIG. 61, a selection of tab 6002 initiates anuplink command queue view in window 6000. In this example, this uplinkcommand queue view is an example of the user interface presented byuplink command queue view 5904 in FIG. 59. In this example, section 6100displays commands for a particular aircraft in a tree queue. A user maydelete a set of commands from section 6100 by selecting those commandsand pressing delete command 6102. The status information about commandsis presented in section 6103.

Information that may be displayed includes, for example, item 6104,expiration 6106, priority 6108, destination system 6110, file type 6112,nomenclature 6114, file size 6116, uplink status 6118, and uplink statusprogress 6120. Item 6104 identifies the particular item, such as anaircraft software part name. Expiration 6106 is an expiration date for aparticular command. Priority 6108 identifies the order in which commandsare to be uplinked to the destination system on the aircraft.Destination system 6110 identifies the particular line replaceable unitin an application on the aircraft in which parts are to be sent. Type6112 identifies the type of item contained in the crate, such as a fileor an aircraft software part.

Nomenclature 6114 provides a short identification or description of thepart. File size 6116 identifies the size of the crate containing theparticular item. Uplink status 6118 provides a status as to the process,success, or failure of a command. Uplink status progress 6120 provides agraphical progress bar showing the percent complete for a particularcommand.

With reference now to FIG. 62, a diagram illustrating a user interfacefor an uplink local inventory view is depicted in accordance with anadvantageous embodiment. In this example, tab 6004 has been selected,and a user interface for uplink local inventory view 5906 in FIG. 59 ispresented. This particular view allows a user to load crates or aircraftsoftware parts from a local source. This type of functionality allows auser to load an aircraft software part from another source in the eventthat access to a library or proxy server application may be unavailableor interrupted. Additionally, new parts that may not be found in thelibrary or proxy server application or updated versions of aircraftsoftware parts also may be loaded in this manner. A local inventory ofaircraft software parts or other items may be found on storage devices,such as a hard drive, a flash memory, a compact disc, or a digitalversatile disc.

Section 6200 illustrates an identification of local inventory that maybe loaded onto the software maintenance tool. These items may includeaircraft software parts and commands. A particular item may be loaded byselecting that item in section 6200 and pressing load inventory frommedia button 6202. The current inventory found on a particular storagedevice may be refreshed by pressing refresh inventory 6204.

Details about selected items in section 6200 may be displayed in section6206. In these examples, the information may include, for example,inventory item 6208, expiration date 6210, airplane identifier 6212,airplane destination 6214, type 6216, nomenclature 6218, file size 6220,uplink status 6222, and uplink status progress 6224. This information issimilar to the information displayed for aircraft software partsreceived from a library proxy server application as displayed in window6000 in FIG. 61.

With reference now to FIG. 63, a diagram of a user interface for adownlinked files view is depicted in accordance with an advantageousembodiment. In this example, window 6000 displays a user interface for auser interface component, such as downlinked files view 5908 in FIG. 59.This view is presented in response to a selection of tab 6006. In thisuser interface, information about data downlinked from differentaircraft is displayed in section 6300.

A user may suspend or stop downlinks from an onboard electronicdistribution system on an aircraft by selecting suspend downlinks button6302. When this button is selected, a software maintenance tool does notreceive any additional downlinks or information from the aircraft towhich the connection is present. Downlinks may be resumed by pressing aresume button that is displayed.

Further, a user may redirect downlinks destined for a proxy serverapplication to the software maintenance tool by selecting redirectdownlinks button 6304. Selection of this button causes the onboardelectronic distribution system to reroute all downlink informationdestined for a proxy server application to be sent to the softwaremaintenance tool. If the software maintenance tool is disconnected fromthe onboard electronic distribution system, the downlinks are thenautomatically sent to the original destination.

Section 6306 displays additional information for downlink data presentedin section 6300. Further, a user may view or delete downlink files insection 6306. Deletions may be made by selecting a particular downlinkfile and initiating the delete command.

Information presented about downlinked files in section 6306 include,for example, file name 6308, airplane identifier 6310, system 6312,application 6314, data type 6316, description 6318, file size 6320,downlink status 6322, and downlink date and time 6324. File name 6308identifies the name of the file downlinked or received from theaircraft. Airplane identifier 6310 identifies the aircraft from whichthe data is received. System 6312 identifies the line replaceable unitfrom which the data is received. Application 6314 identifies theaircraft software part on the line replaceable unit associated with thedata.

Data type 6316 identifies the type of data generated by the application.The software maintenance tool receives downlinked files with a data typeto represent an unsolicited downlink in these examples. Description 6318identifies the name of the file downlinked in this example. File size6320 identifies the size of the downlinked file. Downlink status 6322identifies whether the data was successfully downlinked to the softwaremaintenance tool. Downlink date and time 6324 identifies when thedownlink is completed. This completion may be a successful completion, afailure, or a partial downlink, depending upon the particular situation.

Turning now to FIG. 64, a diagram illustrating a user interface for anevent console is depicted in accordance with an advantageous embodiment.In this diagram, window 6000 displays a user interface for a userinterface component, such as events console view 5910 in FIG. 59. In thedepicted example, this particular view is presented in window 6000 inresponse to selecting tab 6008. Section 6400 presents activity thatoccurs with a particular software maintenance tool session. In theseexamples, a software maintenance tool session is a period of time duringwhich the software maintenance tool is operating. The events illustratedin section 6400 may be presented in real time.

In these examples, these events may be saved by selecting save eventsconsole button 6402. Events may be cleared from display in section 6400by selecting clear events console button 6404. Additionally, thesoftware maintenance tool may automatically save events without userintervention. In these examples, each entry displayed in section 6400includes a date and time stamp, a user identifier of the user performinga particular action, and a message identifying the action that has beenperformed.

Turning now to FIG. 65, a diagram illustrating a user interface for aretrieve from library view is depicted in accordance with anadvantageous embodiment. In this example, window 6000 displays a userinterface for retrieve from library view 5912 in FIG. 59. This userinterface is presented in response to a selection of tab 6010. This userinterface may be used to retrieve commands from a library or a proxyserver application as well as browsing or looking at the variousaircraft software parts. Additionally, this is when the loss may be usedto create commands to uplink aircraft software parts to an onboardelectronic distribution system.

Parts that are available in the library are displayed in section 6500.Particular aircraft software parts designated for the softwaremaintenance tool may be retrieved by pressing perform librarytransactions button 6502. A user also may create commands to uplinkaircraft software parts to an onboard electronic distribution systemusing this interface. A user may also select an aircraft software partfrom section 6500 and designate a particular aircraft and linereplaceable unit using list 6504 and list 6506. List 6504 providesidentifications of aircraft. List 6506 identifies a particular linereplaceable unit on the aircraft for the aircraft software part.

After these identifications have been made, the aircraft software partmay be retrieved from the library by pressing retrieve selectedinventory from library button 6508. Selection of this button causes theaircraft software part to be retrieved and a command to be created touplink the aircraft software part to the aircraft.

Turning now to FIG. 66, a diagram illustrating data flow through asoftware maintenance tool in sending commands and aircraft softwareparts to an aircraft is depicted in accordance with an advantageousembodiment. In this example, data sending flow is shown for softwaremaintenance tool 6600 to the sending of commands and aircraft softwareparts from library 6602 or proxy server application 6604 to onboardelectronic distribution system (OBEDS) 6606 on an aircraft. Each of thedifferent steps and the results of those steps performed by softwaremaintenance tool 6600 may be logged as events for downloading to library6602 or proxy server application 6604.

In this example, the process begins when a user initiates a transactionsprocess with library 6602 or proxy server application 6604 using a userinterface from a user interface component, such as retrieve from libraryview 5912 in FIG. 59. Library service 6608 retrieves a list of uplinkcommands that have been successfully uplinked to onboard electronicdistribution system 6606. Library service 6608 then makes a call toeither library 6602 or proxy server application 6604 and passes a listof the command identifiers for commands that were successfully uplinkedto onboard electronic distribution system 6606. Library service 6608retrieves a list of uplink commands that have been successfully uplinkedfrom commands table 6610. Commands table 6610 is an example of a tablefound in database 6612. Commands table 5500 in FIG. 55 identifies fieldsthat may be found in commands table 6610.

For every command identifier sent to library 6602 or proxy serverapplication 6604, the corresponding command is deleted from commandstable 6610 in database 6612. Additionally, library service 6608 also maysend downlink files and event logs from file system 6614.

Thereafter, library service 6608 may make a call to library 6602 orproxy server application 6604 to obtain a list of commands. Thesecommands are compared with commands that should be in queues fordistribution to different aircraft. If commands are present in commandstable 6610 that are not in the list of commands received from library6602 or proxy server application 6604, those commands are deleted fromthis table. However, commands generated by an operator of softwaremaintenance tool 6600 will be retained. The deletion of commands, inthese examples, occurs for commands previously sent from library 6602 orproxy server application 6604.

For each new command received, library service 6608 determines whether acrate already exists for the aircraft software part within file system6614. If the crate for the aircraft software part is not present for thecommand, then library service 6608 retrieves a crate containing theaircraft software part from library 6602 or proxy server application6604. Any retrieved crates are stored in file system 6614. If the crateis successfully retrieved or a crate already exists, the new command isplaced into commands table 6610 in database 6612. If the crate issuccessfully retrieved or the crate already exists, the new command isadded to a queue in uplink command queue manager 6617. Uplink commandqueue view 6618 may show information for commands managed by uplinkcommand queue manager 6617.

Thereafter, uplink local inventory view 6616 is updated or refreshed. Inthis example, uplink local inventory view 6616 is a user interfacecomponent, such as uplink local inventory view 6004 as displayed inwindow 6000 in FIG. 62. This view allows an operator to see thedifferent aircraft software parts that are stored within the softwaremaintenance tool. By knowing what aircraft software parts are present infile system 6614, an operator may create new commands to uplink thoseaircraft software parts using the software maintenance tool. Thereafter,uplink command queue view 6618 is updated. This view may be, forexample, uplink command queue view 6002 as displayed in window 6000 inFIG. 61.

Thereafter, the operator may disconnect software maintenance tool 6600from library 6602 or proxy server application 6604. Software maintenancetool 6600 may then be transported to the aircraft and connected toonboard electronic distribution system 6606. When this connection isestablished, uplink command queue view 6618 automatically uplinks allcommands that have not been successfully uplinked for the particularaircraft to onboard electronic distribution system 6606 through onground connection (OGC) interface 6620.

On ground connection interface 6620 creates a command for on groundcomponent (OGC) 6622 and adds this command to a list of commands for onground component 6622 to retrieve one at a time. These commands areidentified in uplink command queue manager 6617.

When on ground component 6622 calls on ground component interface 6620,on ground component interface 6620 determines whether the aircraft isalready uplinking data. If the aircraft is already uplinking data, anull value is returned to on ground component 6622, and commands are notchanged in the command list. In these examples, on ground component 6622communicates with onboard electronic distribution system 6606 todetermine whether the aircraft is uplinking data in these examples.

If the aircraft is not already uplinking, the oldest uplink command inthe command queue is passed to on ground component 6622. In turn, onground component 6622 communicates with onboard electronic distributionsystem 6606 to start uplinking the crate identified in the command. Onground component 6622 may obtain status information during uplinking ofaircraft software parts. Further, on ground component interface 6620 mayupdate uplink command queue view 6618 to show a progress bar, such asthose illustrated in uplink status progress 6120 in FIG. 61.

When the command has been successfully executed, uplink command queueview 6618 updates the information in commands table 6610. Additionally,uplink command queue view 6618 also updates the execution status of thecommand field in commands table 6610.

Turning now to FIG. 67, a diagram illustrating data flow in a softwaremaintenance tool processing downlinked files is depicted in accordancewith an advantageous embodiment. In this example, software maintenancetool 6700 may receive downlinked files initiated by application 6702executing on a laptop computer connected to onboard electronicdistribution system (OBEDS) 6704. Additionally, unsolicited downlinkfiles from line replaceable units (LRU's) 6706 also may be received bysoftware maintenance tool 6700. When software maintenance tool 6700establishes a connection to onboard electronic distribution system 6704,on ground component 6708 is the component that provides thecommunication with onboard electronic distribution system 6704.

On ground component (OGC) 6708 communicates through on ground component(OGC) interface 6710 with other components in software maintenance tool6700. In this example, a downlink file is downlinked and stored in filesystem 6712. When the downlink file is transferred to file system 6712,on ground component interface 6710 inserts a new record in downlinkstable 6714 in database 6716.

The different downlink files stored within file system 6712 may beviewed using downlinked files view 6718. This view is an example of auser interface component, such as downlinked files view 5908 in FIG. 59.This view may be used to identify what downlink files have been receivedas well as manipulate downlink files. Downlinks table 5700 in FIG. 57shows examples of fields that may be found in downlinks table 6714.

Thereafter, software maintenance tool 6700 may be moved and establish aconnection with library 6720 or proxy server application 6722. When thisconnection is established, library service 6724 identifies downlinkfiles that have not yet been sent to library 6720 or proxy serverapplication 6722. The identification of these files may be found indownlinks table 6714.

In these examples, partially downlink files are not sent to library 6720or proxy server application 6722. For each of the downlink filesidentified in downlinks table 6714, library service 6724 confirms thatthese files are still stored in file system 6712. Library service 6724then forwards all of the located downlinked files to library 6720 orproxy server application 6722. Any files sent to proxy serverapplication 6722 are eventually sent to library 6720 by proxy serverapplication 6722.

In some cases, files may be only partially downlinked to the softwaremaintenance tool because of an interruption. The different advantageousembodiments provide a mechanism through which partially downlinked filesare saved by the software maintenance tool within file system 6712.These partial downlinked files are saved, and additional or remainingportions of the downlink may be retrieved at a later time and added tothese partial downlinked files to form a complete downlink file. In thismanner, if an interruption occurs, the downlinking of data may pick upwhere it left off without having to downlink the entire file again.

Turning now to FIG. 68, a diagram illustrating data flow and loggingimporting events by a software maintenance tool is depicted inaccordance with an advantageous embodiment. In this example, softwaremaintenance tool 6800 logs events in file system 6802 using processevent logger 6804. Process event logger 6804 is an example of a processthat may be found in manager 5408 in FIG. 54.

In these examples, process event logger 6804 may log all of thedifferent steps and results of those steps performed by softwaremaintenance tool 6800 in uplinking and downlinking data. This type ofinformation may be displayed in event console view 6806, which is anexample of a user interface component in user interface components 5900in FIG. 59. An example user interface is window 6000 in FIG. 64. Whensoftware maintenance tool 6800 connects to library 6808 or proxy serverapplication 6810 through library service 6812, a user input is receivedto transfer data and log files stored in file system 6802 and areforwarded on to library 6808 and proxy server application 6810. If theevent logs are successfully sent, the event log files are renamed forarchival purposes.

Turning now to FIG. 69, a diagram illustrating data flow in a softwaremaintenance tool retrieving parts from a library is depicted inaccordance with an advantageous embodiment. In this example, softwaremaintenance tool 6900 may connect to library 6902 or proxy serverapplication 6904 through library service 6906. A user may retrieve fromlibrary view 6908 to identify parts stored on library 6902 and/or proxyserver application 6904.

Retrieve from library view 6908 is an example of retrieve from libraryview 5912 in FIG. 59 within user interface components 5900 in FIG. 59.Window 6000 in FIG. 65 is an example of a user interface for thisparticular view. The parts may be displayed and retrieved from retrievefrom library view 6908. A user may select a set of parts and retrievethose parts from library 6902 and/or proxy server application 6904 andstore the aircraft software parts in file system 6910. The parts arethen displayed for users to create uplink command(s).

Turning now to FIG. 70, a diagram illustrating data flow in a softwaremaintenance tool during retrieving and creating of commands is depictedin accordance with an advantageous embodiment. In this example, softwaremaintenance tool 7000 may retrieve parts and create commands usingretrieve from library view 7002. Retrieve from library view 7002 is anexample of a user interface component, such as retrieve from libraryview 5912 in FIG. 59 as presented in window 6000 in FIG. 65.

When library service 7004 is connected to library 7006 or proxy serverapplication 7008, a user may view a list of parts retrieved fromretrieve from library view 7002. A user may select parts through thisview and initiate downlinking of those parts by library service 7004.The parts retrieved by library service 7004 are stored in file system7010. In these examples, the aircraft software parts are stored ascrates. Uplink local inventory view 7012 may be refreshed.

With retrieve from library view 7002, a user may create commands thatare stored in commands table 7014 in database 7018. These commands maybe added to uplink command queue manager 7020 for execution by on groundcomponent (OGC) 7022 through on ground component (OGC) interface 7024 toonboard electronic distribution system (OBEDS) 7026. Uplink commandqueue manager 7020 is an example of a component within manager 5408 insoftware maintenance tool 5400 in FIG. 54. The status of this processmay be viewed through uplink command queue view 7028.

With reference now to FIG. 71, a diagram illustrating uploading ofaircraft software parts from alternative sources is depicted inaccordance with an advantageous embodiment. In this example, softwaremaintenance tool 7100 may upload aircraft software parts from media 7102into file system 7104 through uplink local inventory manager 7106. Thisview is an example of uplink local inventory view 5906 in FIG. 59. Thisview uses a graphical user interface, such as window 6000 in FIG. 62.

The control of this uploading or uplinking process from media 7102 maybe performed using uplink local inventory view 7108. Aircraft softwareparts may be uploaded into software maintenance tool 7100 from othersources other than a library or a software proxy server application. Byallowing for this type of flexibility, software maintenance tool 7100may allow for last minute parts or new parts not yet available fromnormal sources to be uploaded to an aircraft or if a connection to thelibrary or proxy server application is unavailable.

Turning next to FIG. 72, a high level flowchart of a process formanaging aircraft software parts is depicted in accordance with anadvantageous embodiment. The process illustrating in FIG. 72 may beimplemented in a software maintenance tool, such as software maintenancetool 5400 in FIG. 54.

The process begins by establishing a connection between a portable dataprocessing system and a source through a ground network to form anestablished connection (operation 7200). Thereafter, the processretrieves a set of uplink commands from a source through the establishedconnection (operation 7202). The source may be for example, a proxyserver application, a library, or even a local storage device.

The process then retrieves a set of aircraft software partscorresponding to the set of uplink commands from the source through theestablished connection to form a set of retrieved aircraft softwareparts (operation 7204). The process stores the set of retrieved aircraftsoftware parts in the portable data processing system to form a set ofstored aircraft software parts (operation 7206).

The process then disconnects the portable data processing system withthe stored aircraft software parts from the ground network (operation7208). In these examples, the portable data processing system is movedto a location to allow the portable data processor to connect to anaircraft network on an aircraft. Next, the process connects the portabledata processing system with the stored aircraft software parts to anaircraft data processing system in an aircraft (operation 7210).

The process then issues an uplink command from the set of uplinkcommands to the aircraft data processing system through an on groundcomponent in the portable data processing system (operation 7212). Theprocess sends a stored aircraft software part corresponding to theuplink command in the set of stored aircraft software parts to theaircraft data processing system through the on ground component(operation 7214), with the process terminating thereafter.

Turning now to FIG. 73, a more detailed flowchart of a process formanaging aircraft software parts is depicted in accordance with anadvantageous embodiment. The process illustrated in FIG. 73 may beimplemented in a software maintenance tool, such as software maintenancetool 5400 in FIG. 54. The process in this figure illustrates thedifferent steps that occur in a software maintenance tool when connectedto a source, such as a library or a proxy server application.

The process begins by receiving a request to perform transactions(operation 7300). In this example, the process to perform transactionsmay be initiated by a user through a user interface within userinterface components 5900 in FIG. 59. In particular, the process may beinitiated by a user entering user input into retrieve from library view5912 in FIG. 59 with a user interface, such as window 6000 asillustrated in FIG. 65.

The process then retrieves a list of uplink commands sent to an onboardelectronic distribution system (operation 7302). In this example, thelist of uplink commands are ones in which the aircraft software partsidentified by the uplink command has been successfully sent to theonboard electronic distribution system. These different commands may bestored in a table in a database, such as commands table 5500 in FIG. 55.Each of the records within commands table 5500 in FIG. 55 may include anindication as to whether a command was successfully sent.

Thereafter, the process calls a source (operation 7304). The source maybe, for example, a library or a proxy server application. The processsends these lists of commands to the source (operation 7306). Thecommands sent to the source are then deleted from the database and thesoftware maintenance tool (operation 7308).

The process then calls the source to retrieve new commands (operation7310). A list of commands is received from the source (operation 7312).In operation 7312, the commands are received in an uncrated form unlikethe manner in which a proxy server or application receives commands froma library. The process then deletes commands not in the list from thedatabase (operation 7314). As a result, the source is the authority orprovides an override as to what commands are to be executed by thesoftware maintenance tool.

If a user desires to remove commands or delete commands for execution onan aircraft, these commands may be deleted at the source. The list ofcommands sent to the software maintenance tool results in any commandsnot in the list being deleted. As a result, this type of process allowsfor updating commands to be executed on the software maintenance tool.

The process selects an unprocessed command for processing (operation7316). A determination is made as to whether a crate containing anaircraft software part is present for the command (operation 7318). Inoperation 7318, the process checks the file system on the softwaremaintenance tool to determine whether a crate containing the aircraftsoftware part is already stored in the file system. If a crate is notpresent, then the process retrieves the crate (operation 7320).

Next, a determination is made as to whether additional unprocessedcommands are present (operation 7322). If additional unprocessedcommands are present, the process returns to operation 7316. The processproceeds to operation 7322 from operation 7318 if a crate is present forthe command. The process then adds the commands to a queue (operation7324). The process then updates the inventory of aircraft software parts(operation 7326), with the process terminating thereafter.

FIG. 74 illustrates operations that occur in a software maintenance toolwhen a portable data processing system, on which the softwaremaintenance tool is located, is connected to an aircraft network.

In these examples, the software maintenance tool may be used to sendaircraft software parts to an onboard electronic distribution systemexecuting on an aircraft data processing system in the aircraft network.In these examples, the queue may be, for example, a queue in uplinkcommand queue manager 6617 in FIG. 66. The process then updates aninventory of aircraft software parts (operation 7326), with the processterminating thereafter.

Turning now to FIG. 74, a flowchart of a process for sending aircraftsoftware parts from a software maintenance tool to an onboard electronicdistribution system is depicted in accordance with an advantageousembodiment. In this example, the process may be implemented in asoftware maintenance tool, such as software maintenance tool 5400 inFIG. 54. The process begins by detecting a connection to the onboardelectronic distribution system on the aircraft data processing system(operation 7400).

The process determines whether a command is present in the command queue(operation 7402). If a command is present, the process determineswhether the aircraft is currently uplinking data (operation 7404). Ifthe aircraft is not currently uplinking data, the process sends arequest to the onboard electronic distribution system to uplink thecrate containing the aircraft software part (operation 7406). Theprocess then obtains the status of the uplink (operation 7408). Thestatus may be displayed on a user interface, such as window 6000 in FIG.61. Operation 7408 occurs while uplinking of the crate continues.

After uplinking completes, a determination is made as to whether theuplinking of the crate with the aircraft software part has beensuccessful (operation 7410). If the uplinking of the crate wassuccessful, the command table is updated (operation 7412). The table, inthese examples, is a commands table, such as commands table 5500 in FIG.55. The process then returns to operation 7402 to determine whetheradditional commands are present in the queue for processing.

With reference again to operation 7410, if the uplinking of the aircraftsoftware part was not successful, an error is generated (operation7416), and the process returns to operation 7402 as described above.With reference again to operation 7404, if the aircraft is uplinkingdata, a null value is returned (operation 7414), with the processterminating thereafter.

With reference now to FIG. 75, a flowchart of a process for receivingdownlink data is depicted in accordance with an advantageous embodiment.The process illustrated in FIG. 75 may be implemented in a data softwaremaintenance tool, such as software maintenance tool 5400 in FIG. 54.

The process in FIG. 75 begins by receiving a call from the onboardelectronic distribution system to retrieve a partial downlink file(operation 7500). A determination is made as to whether the partialdownlink file is contained in a partial downlinks table (operation7502). This partial downlink table may be a table such as, for example,partial downlink table 5600 in FIG. 56. If the partial downlink file isnot found in the table, the process receives a call to obtain a handleto the downlink file from the onboard electronic distribution system(operation 7504).

Next, a determination is made as to whether enough disk space is presentto store the downlink file (operation 7506). If sufficient space ispresent, the downlink file is created in a directory called“downlinks/”, and a file handle is returned to the onboard electronicdistribution system (operation 7508). The process then stores thedownlink data into the downlink file in the “downlinks/” directory(operation 7510).

A determination is then made as to whether the downlink file wassuccessfully stored (operation 7512). If all of the downlink data wassuccessfully stored, the process adds the downlink file to the downlinksdatabase table (operation 7514). This table may be a table such as, forexample, downlinks table 5700 in FIG. 57. The process then updates thedownlink files view to show the new file (operation 7516). This view isa view, such as downlinked files view 6006 as presented in window 6000in FIG. 63.

The process then determines whether the data is written to a partialdownlink file (operation 7518). If the data is not written to a partialdownlink file, the process terminates. Otherwise, the partial downlinkrecord in the partial downlinks table is deleted (operation 7520), withthe process terminating thereafter. In this case, the partial downlinkfile is completed with the rest of the downlink data, and theidentification of the partial downlink file is no longer needed.

With reference again operation 7512, if the storing of all of the datafor the downlink file was not successful, the process receives a callfrom the onboard electronic distribution system to store the partialdownlink file (operation 7522). In this case, the onboard electronicdistribution system may have interrupted the downlinking data for anumber of different reasons. For example, the amount of bandwidthavailable is insufficient to downlink data and uplink other information.The process then creates a record in the partial downlinks databasetable (operation 7524), with the process terminating thereafter.

With reference again to operation 7506, if insufficient space is presentfor the downlink file, a null is returned to the onboard electronicdistribution system to indicate that insufficient disk space is presentfor the downlink data (operation 7526). With reference back to operation7502, if a partial downlink file is present in the partial downlinkstable, the process returns partial downlink file information to theonboard electronic distribution system (operation 7528). Thisinformation includes a starting point or offset to send the rest of thedownlink data for the downlink file. The process then proceeds tooperation 7510 as described above.

Thus, the software maintenance tool described in these differentadvantageous embodiments provides an additional feature for transferringaircraft software parts from a library to an aircraft data processingsystem. In the different advantageous embodiments, the softwaremaintenance tool may connect either to the library or to a proxy serverapplication on a ground network to receive commands and aircraftsoftware parts. The software maintenance tool may then be disconnectedfrom the ground network and physically moved to a location forconnection to an aircraft network. At this location, the softwaremaintenance tool connects to the aircraft network and transfers aircraftsoftware parts and commands to the onboard electronic distributionsystem executing on a data processing system on the aircraft network inthe aircraft.

Additionally, the software maintenance tool allows for an operator tocreate commands independently from the library using graphical userinterfaces presented by view components in the software maintenancetool. The software maintenance tool also includes features that allowthis component to receive aircraft software parts from other sourcesother than a library or proxy server application.

The different advantageous embodiments also provide a computerimplemented method, apparatus, and computer program product fortransferring information with an aircraft. In one advantageousembodiment, a computer implemented method is used for transferringinformation with the aircraft. A connection is established between anonboard electronic distribution system executing in an aircraft dataprocessing system in the aircraft and an on ground component.

The on ground component may be located in a ground network in a softwareapplication, such as a software maintenance tool or a proxy serverapplication, in these examples. In response to a request for a commandfrom the onboard electronic distribution system made through theconnection, the command for execution by the onboard electronicdistribution system is identified. This identified command is sent tothe onboard electronic distribution system from the on ground component.A transaction identifier is assigned to the command.

A status of the transaction associated with the command is maintained onthe onboard electronic distribution system and on the on groundcomponent using the transaction identifier. An uplink is initiated bythe onboard electronic distribution system. An aircraft software part isthen sent to the onboard electronic distribution system from the onground component to perform the uplink. The status of this transfer isstored.

Turning now to FIG. 76, a diagram of components used to transferinformation with an aircraft is depicted in accordance with anadvantageous embodiment. Onboard electronic distribution system 7600 isan example of an onboard electronic distribution system, such as onboardelectronic distribution system 310 in aircraft software part managementapparatus 300 in FIG. 3.

In this illustrative example, onboard electronic distribution system7600 and mass storage 7602 are components located on an aircraft dataprocessing system in an aircraft network. Onboard electronicdistribution system 7600 is an example of onboard electronicdistribution system 146 in FIG. 1. Mass storage 7602 is an example ofstorage device 148 in FIG. 1. These components are part of an aircraftdata processing system, such as aircraft data processing system 144 inaircraft network 101.

On ground component 7604 and on ground component interface 7606 areexamples of components that may be found in a proxy server applicationor a software maintenance tool, such as proxy server application 3500 inFIG. 35 or software maintenance tool 5400 in FIG. 54. In these examples,on ground component 7604 and onboard electronic distribution system 7600may exchange information. Command 7607, aircraft software part 7608,downlink file 7610, and status 7612 are examples of information that maybe transferred with onboard electronic distribution system 7600.

In these examples, on ground component 7604 may send command 7607 toonboard electronic distribution system 7600. Onboard electronicdistribution system 7600 may execute this command to perform atransaction. This transaction may be, for example, an uplink or adownlink of data. An uplink includes sending aircraft software part 7608to onboard electronic distribution system 7600. A downlink includessending downlink file 7610 to on ground component 7604.

Additionally, the status of the different transactions is maintained byboth on ground component 7604 and onboard electronic distribution system7600 in these examples. Status 7612 is sent by onboard electronicdistribution system 7600 to on ground component 7604 to provide thestatus of a particular transaction being performed through the executionof a command, such as command 7607. This status is associated with aparticular command or transaction through a command identifier.

Aircraft software part 7608 may be sent to onboard electronicdistribution system 7600 for storage with aircraft software parts 7614in mass storage 7602. Downlink file 7610 may be a downlink file fromdownlink files 7616 in mass storage 7602.

Status information 7618 may be stored in mass storage 7602 and includesstatus information, such as status 7612. Status information 7618 mayindicate that a particular aircraft software part has been successfullystored within aircraft software parts 7614 in mass storage 7602. Statusinformation 7618 allows for the initiation of the loading of an aircraftsoftware part from mass storage 7602 onto a line replaceable unit oncethat aircraft software part has been identified as being successfullyuplinked by onboard electronic distribution system 7600 and storedwithin mass storage 7602.

Additionally, status information 7618 may identify whether a downlinkfile, such as downlink file 7610, has been successfully downlinked. If apartial downlink of downlink file 7610 occurs, status information 7618provides the status of what information within downlink file 7610 hasbeen transmitted. As a result, maintaining a status of how muchinformation has been downlinked to on ground component 7604 may be usedto downlink the remaining information for downlink file 7610 at a laterpoint in time without restarting the entire transmission of downlinkfile 7610.

On ground component interface 7606 provides an interface with othercomponents to on ground component 7604. In this manner, on groundcomponent 7604 may be interchangeable or modified with other versions orconfigurations of on ground components to provide access to a particularonboard electronic distribution system that may have a differentprotocol for exchanging information or processing commands. In theseexamples, on ground component 7604 contains the processes needed totransfer information with onboard electronic distribution system 7600.If a different onboard electronic distribution system is employed thatis not compatible with on ground component 7604, on ground component7604 may be substituted with another on ground component.

As a result, other software components in the ground network do not haveto be changed. For example, other components within a proxy serverapplication and a software maintenance tool do not require modificationsto be able to communicate with an onboard electronic distributionsystem.

Turning now to FIG. 77, a message flow diagram illustrating message flowused to poll for a command is depicted in accordance with anadvantageous embodiment. In this example, the components involved inthis message flow are on ground component (OGC) interface 7700, onground component 7702, and onboard electronic distribution system 7704.

In this example, onboard electronic distribution system 7704 polls onground component 7702 for a command (message T1). In response to beingpolled, on ground component 7702 sends a get command request to onground component interface 7700 (message T2). This command is used by onground component interface 7700 to identify commands that may be locatedin a proxy server application or a software maintenance tool for onboardelectronic distribution system 7704.

In response, a command or a pointer to a crated command file is returnedto on ground component 7702 (message T3). In these examples, a proxyserver application returns a pointer, such as a universal resourcelocator, to a crated file containing the command. With a softwaremaintenance tool, the actual command itself is returned in message T3.If a command is not present, then a null value or some other indicatoris returned in message T3. The returned command is then sent to onboardelectronic distribution system 7704 (message T4). Onboard electronicdistribution system 7704 may then process and execute the commandreceived in message T4.

Turning now to FIG. 78, a message flow diagram illustrating the sendingof status information is depicted in accordance with an advantageousembodiment. In this example, components in the message flow include onground component interface 7700, on ground component 7702, and onboardelectronic distribution system 7704. Onboard electronic distributionsystem 7704 provides status information for various operations andprocesses executed by onboard electronic distribution system 7704. Thisstatus information may include, for example, the status of an aircraftsoftware part that has been uplinked, the status of a downlink file,and/or other suitable information.

Onboard electronic distribution system 7704 sends the status to onground component 7702 (message U1). This status is relayed by on groundcomponent 7702 to on ground component interface 7700 (message U2). Thisstatus information may then be processed by a proxy server applicationor a software maintenance tool in these examples.

Two phases are present for downlinking data. FIG. 79 illustrates a firstphase in which a request for downlinking data is made, and FIG. 80depicts a second phase in which the data is downlinked. With referencenow to FIG. 79, a message flow diagram of a request to downlink data isdepicted in accordance with an advantageous embodiment. The message flowin FIG. 79 shows the first phase in downlinking data. In these examples,FIG. 79 shows the request to downlink data. The second phase is foractually transmitting downlink data as described with respect to FIG.80, below.

In this example, phase one has two cases. In case 7902, a request todownlink information is made with a partial downlink being available.

In case 7900, onboard electronic distribution system 7704 sends arequest to downlink a file (message V1). In message V1, the request maybe refused if no space is present to store the downlink file. Inresponse, on ground component 7702 sends a request to determine whethera partial downlink record is present to on ground component interface7700 (message V2). In response, on ground component interface 7700 sendsa request to obtain a partial downlink associated with the request tosend to message V1 (message V2). The request sent in message V2 includesan airplane identifier and a downlink identifier. This information isused by on ground component interface 7700 to determine whether apartial downlink file is present for this particular downlink file.

On ground component interface 7700 returns a null value to on groundcomponent 7702 indicating that a partial downlink file is not presentfor the requested downlink (message V3). In response, on groundcomponent 7702 makes a request to downlink the downlink file (messageV4). The message in message V4 is a request to downlink the entire filein these examples. In these examples, the message includes informationabout the file size. If space is available, on ground componentinterface 7700 returns a location to downlink the file to on groundcomponent 7702 (message V5). If no space is available, a null value isreturned to message V5.

In response, on ground component 7702 returns a response to onboardelectronic distribution system 7704 (message V6). This message is eitheran indication that is an okay to proceed downlinking or a denial of therequest.

In case 7902 in the first phase, onboard electronic distribution system7704 makes a request to downlink part of a file for a downlink file(message V7). In response, on ground component 7702 makes a request todetermine whether a partial downlinked file is already present for therequested downlink (message V8).

In response to receiving this message, on ground component interface7700 returns a document containing a reference to an existing partiallydownlinked file to on ground component 7702 (message V9). In theseexamples, the document is an extensible markup language (XML) document,and reference may be a pointer or universal resource locator (URL)depending on the particular implementation.

When the reference is returned, on ground component 7702 sends aresponse to the request to downlink a partial downlink file to onboardelectronic distribution system 7704 (message V10). The response, in thisexample, includes an indication that it is okay to proceed with thedownlink and an offset to use. The offset identifies where in thedownlink file the downlinking of data should start. This offset isidentified from the downlink information already received for thedownlink file.

Turning now to FIG. 80, a message flow diagram for downlinking data isdepicted in accordance with an advantageous embodiment. As with FIG. 79,this downlink process includes two cases, case 8000 and case 8002. Case8000 involves downlinking data with no partial downlinks, and phase 8002involves downlinking data with partial downlinks. In FIG. 79, case 7900illustrates the case in which a partial downlink is not available, whilecase 7902 illustrates the case in which a partial downlink file isavailable on the on ground component.

In case 8000, the message flow begins with onboard electronicdistribution system 7704 downlinking the downlink file to on groundcomponent 7702 (message W1). On ground component 7702 makes a request todownlink the file from onboard electronic distribution system 7704 to onground component interface 7700 (message W2). This message includes afile size as well as other suitable downlink information.

On ground component interface 7700 returns a response to on groundcomponent 7702 (message W3). A null is returned if space is unavailableto downlink the downlink file. If the downlink file can be downlinked,on ground component 7702 writes the information into a file and returnsa response to onboard electronic distribution system 7704 (message W4).Thereafter, on ground component 7702 makes a request to on groundcomponent interface 7700 to store the file (message W5).

Next, in case 8002, onboard electronic distribution system 7704downlinks a file to on ground component 7702 (message W6). Thereafter,on ground component 7702 requests the partial downlink file from onground component interface 7700 (message W7). In this example, the fileis returned to on ground component 7702 by on ground component interface7700 (message W8).

At this time, on ground component 7702 writes information into the fileto complete the downlink file and returns a response to onboardelectronic distribution system 7704 (message W9). In this example, thenumber of bits written in the file is identified in the response.Thereafter, on ground component 7702 sends a request to on groundcomponent interface 7700 to store the downlinked file (message W10).

In response to this message, on ground component interface 7700 maystore the file within the file system of the ground component. Theground component may be a file stored in a proxy server application or asoftware maintenance tool.

With reference now to FIG. 81, a diagram illustrating message flow whenthe file is only partially delivered is depicted in accordance with anadvantageous embodiment. In this example, onboard electronicdistribution system 7704 downlinks a file using a normal downlinksequence in which the connection fails or stops (message X1). Inresponse to only receiving part of the file, on ground component 7702sends a request to on ground component interface 7700 to store thepartial downlink file (message X2). In response to receiving thisrequest, the partial downlink file is stored in a file system by onground component interface 7700. This file system may be located in aproxy server application or a software maintenance tool.

Turning now to FIG. 82, a message flow diagram illustrating an uplinkprocess is depicted in accordance with an advantageous embodiment.Uplinking is performed in two phases in these examples. In phase 8200,information about the file to be uplinked is requested, and in phase8202, the file itself is uplinked. In both phases, on ground component7702 prompts the ground system for information about the resource. Theground system may be, for example, other components in a proxy serverapplication or software maintenance tool.

As depicted, onboard electronic distribution system 7704 sends a messagerequesting the uplink of an aircraft software part (message Y1). Inresponse to receiving this request, on ground component 7702 sends acall to obtain the particular aircraft software part to on groundcomponent interface 7700 (message Y2). In response to this call, anidentification of the aircraft software part is returned if the aircraftsoftware part is present (message Y3).

If the part is not present, a null value is returned in these examples.In response to receiving this message, on ground component 7702 relaysthe message to onboard electronic distribution system 7704 (message Y4).

In phase 8202, onboard electronic distribution system 7704 requests theaircraft software part (message Y5). In response to receiving thisrequest, on ground component 7702 requests the aircraft software partfrom on ground component interface 7700 (message Y6). On groundcomponent interface 7700 returns the resource if it is available(message Y7). If the resource is not available, a null value isreturned. On ground component 7702 then sends the aircraft software partto onboard electronic distribution system 7704 (message Y8). If theaircraft software part is not available, then an error is returned.

Turning now to FIG. 83, a diagram illustrating message flow in an uplinkprocess is depicted in accordance with an advantageous embodiment. Inthis example, two phases are present in the message flow, phase 8300 andphase 8302. In phase 8300, a request is made for a partial uplink of anaircraft software part, and in phase 8302, the uplink of the partialaircraft software part is performed. This partial uplinking of anaircraft software part may be performed if a previous transfer of theaircraft software part was interrupted.

In phase 8300, onboard electronic distribution system 7704 sends anuplink request to on ground component 7702. In this example, the requestidentifies the aircraft software part in an offset or start positionfrom which the part should be uplinked (message Z1). In response toreceiving this request, on ground component 7702 requests the aircraftsoftware part (message Z2).

On ground component interface 7700 returns the aircraft software part ifthe part is present. Otherwise, a null value is returned (message Z3).In response to receiving the aircraft software part, on ground component7702 returns a response indicating that the aircraft software part isavailable at the particular offset or starting point (message Z4).

Next, in phase 8302, onboard electronic distribution system 7704requests the aircraft software part at the start or offset position(message Z5). On ground component 7702 requests the resource in responseto receiving this request (message Z6).

In response to receiving the request, on ground component interface 7700returns the aircraft software part, or a null value if the part isunavailable, to on ground component 7702 (message Z7). Responsive toreceiving the response, on ground component 7702 begins uplinking theaircraft software part at the start point or offset identified (messageZ8). If the part is unavailable, an error is returned to onboardelectronic distribution system 7704.

Turning now to FIG. 84, a flowchart of a process for uplinking data isdepicted in accordance with an advantageous embodiment. The processillustrated in FIG. 84 may be implemented in an onboard electronicdistribution system, such as onboard electronic distribution system 7600in FIG. 76. In this example, the uplink data is for an aircraft softwarepart.

The process begins by receiving an uplink command to uplink an aircraftsoftware part (operation 8400). A determination is made as to whetherthe aircraft software part has already been partially uplinked(operation 8402). If the aircraft software part has not been partiallyuplinked, a request is made to receive the aircraft software part(operation 8404). The process then receives data for the aircraftsoftware part (operation 8406).

A determination is made as to whether the transmission of the data hasstopped (operation 8408). The transmission may stop for a number ofreasons. For example, the transfer of an aircraft software part may havecompleted. In another example, an interruption may have occurred withoutcompleting the transfer of the aircraft software part.

The interruption may also occur due to various events. In one event, thecommunications link between the onboard electronic distribution systemand the on ground component may have terminated unexpectedly. In anotherexample, the event may be an operator terminating the transmission ofthe aircraft software part from a software maintenance tool.

If the transmission of data has not stopped, the process returns tooperation 8406. Otherwise, a determination is made as to whether theaircraft software part is complete (operation 8410). If the aircraftsoftware part is complete, the aircraft software part is stored in astorage device in the aircraft data processing system (operation 8412).In this example, the storage device may be mass storage 7602 in FIG. 76.

The process then returns a status to the on ground component (operation8414), with the process terminating thereafter. In this example, thestatus indicates that the aircraft software part has been completelyreceived.

With reference again to operation 8410, if the aircraft software parthas not been completely received, the received portion of the aircraftsoftware part is stored in a storage device (operation 8416). Theprocess then stores the status (operation 8418), with the processterminating thereafter. In this illustrative example, the status mayidentify the aircraft software part and the portion of the aircraftsoftware part that has actually been received. This information may beused at a later point to retransmit the remaining portion of theaircraft software part.

With reference again to operation 8402, if the aircraft software parthas been partially uplinked, the process requests the unsent portion ofthe aircraft software part (operation 8420). The process then proceedsto operation 8406 to receive data from the aircraft software part. Inoperation 8420, the request may include an identification of the offsetor start point for the aircraft software part data that has not yet beenreceived.

Turning now to FIG. 85, a flowchart of a process for downlinking data isdepicted in accordance with an advantageous embodiment. The processillustrated in FIG. 85 may be implemented in an onboard electronicdistribution system, such as onboard electronic distribution system 7600in FIG. 76.

The process begins by sending a request to send a downlink file(operation 8500). A determination is made as to whether an indication isreceived to send the data for the downlink file (operation 8502). If anindication is received to send the data, the process sends the downlinkdata for the downlink file (operation 8504).

Next, a determination is made as to whether the transmission of thedownlink data has stopped (operation 8506). The transmission may stopbecause all of the data has been sent. In other instances, for example,the transmission may stop due to a loss of a communications link or aninterruption by an operator on the aircraft. If the transmission of thedata has not stopped, the process returns to operation 8504 to continueto send downlink data.

If the transmission has stopped, a determination is made as to whetherall of the downlink data has been sent from the downlink file (operation8508). If all of the downlink data has been sent, the process sends astatus of the completion (operation 8510), with the process terminatingthereafter.

With reference again to operation 8508, if all of the downlink data hasnot been sent, a status of the transmission of the downlink data isstored (operation 8512). In these examples, the status may be stored asstatus information 7618 in FIG. 76. The status, in this example, mayidentify the downlink file and the amount of data that was sent.

This process also may be used to send a partial downlink file in which aportion of the downlink file has already been sent. With this type ofdownlinking, operation 8500 sends a request to downlink a portion of thedownlink file rather than the entire file. With a partial downlink file,operation 8502 is a positive indication if the on ground component findsthe partially downlinked data from a previous transmission. Thisindication also includes an offset or starting point to send the rest ofthe downlink file.

Aircraft software parts may be received from various sources. Aircraftsoftware parts may be received from a manufacturer of the aircraft orsome third party source, depending on the particular implementation.Further, an airline also may create aircraft software parts for usewithin its aircraft. These parts are distributed using crates in thedifferent advantageous embodiments.

The different advantageous embodiments provide a computer implementedmethod, apparatus, and computer program product that promotes automationof the receipt and distribution processing digitalized content, computerprogram(s), or data in digital form that is sensible by a computer. Oneadvantageous embodiment includes the replacement of the physicalshipping crate and physical media with a computer sensible crate thatfacilitates automation. Another advantageous embodiment is theapplication of one or more digital signatures to the objects inside thecrate and to the crate itself. Thus, in conjunction with a functioningPrivate Key Infrastructure, it provides authentication of the sender,non-repudiation, and assurance of integrity.

In another advantageous embodiment, a method is used for automatedprocessing aircraft software parts. An incoming crate, which can be anelectronic zip file, containing a signed aircraft software part isreceived from a source outside of an airline's part management system. Aset of signatures is validated for the incoming crate and the aircraftsoftware part. Responsive to the set of signatures being valid, theincoming crate is unpacked. The contents of the incoming crate may bedisplayed at the user's discretion. Responsive to a request to uploadthe unpacked aircraft software part to a library in an aircraft softwarepart management system or apparatus, the unpacked aircraft software partis signed again with an approval signature to form a signed, approvedaircraft software part. An advantageous embodiment is that this secondapproval digital signature also acts to transfer bailment from theprovider of the part to the recipient of the part and providesnon-repudiation of the consummation of the transaction.

In an advantageous embodiment, the crate containing the signed,recipient approved aircraft software part is signed to form a signedcrate wherein signatures for the signed, approved aircraft software partand the signed crate are different from the set of signatures on theincoming crate. The signed crate may be sent to the recipient's libraryin the aircraft software part management system or apparatus.

In another advantageous embodiment, a computer implemented method isused for processing additional configuration items. A crate containing aconfiguration item is received to form a received crate. A determinationis made as to whether a set of signatures for the crate and theconfiguration item are valid. Responsive to a determination that the setof signatures are valid, the configuration item is stored.

Turning now to FIG. 86, a diagram illustrating a crate tool is depictedin accordance with an advantageous embodiment. Crate tool 8600 is usedto receive and manage crates for use in an environment, such as aircraftsoftware part management apparatus 300 in FIG. 3.

Additionally, crate tool 8600 may be implemented in other components forcreating crates within aircraft software part management apparatus 300in FIG. 3. For example, the functionality of crate tool 8600 may beimplemented in a software maintenance tool, such as software maintenancetool 5400 in FIG. 54. As another example, these functions also may beimplemented in aircraft network 101 in FIG. 1 to send information, suchas downlink files in crates, back to a ground network.

In this example, crate tool 8600 may receive aircraft software part 8602stored or wrapped within crate 8604. Although these examples illustrateaircraft software part 8602 as being the contents of crate 8604, anyconfiguration item may be placed into crate 8604 for use within aircraftsoftware part management apparatus 300 in FIG. 3, in these examples. Forexample, a configuration item also may take the form of a document,configuration information, or other suitable information.

Crate tool 8600 processes crate 8604 for uploading to library 8606.Library 8606 may be implemented using library 1700 in FIG. 17. Thisprocessing may include various functions, such as checking the integrityand a set of signatures within crate 8604. The checking of signaturesmay include both the signature for crate 8604 and aircraft software part8602. Further, aircraft software part 8602 may be removed from crate8604 and inspected. Crate tool 8600 also may repackage aircraft softwarepart 8602 into another crate for uploading to library 8606.

Turning now to FIG. 87, a diagram illustrating a crate tool is depictedin accordance with an advantageous embodiment. Crate tool 8700 is a moredetailed illustration of crate tool 8600 in FIG. 86. Crate tool 8700includes user interface 8702, signature 8704, unpack and inspect 8706,crate 8708, and upload 8710. User interface 8702 provides a userinterface for a user to operate crate tool 8700. Crate tool 8700 may beimplemented in a data processing system, such as data processing system200 in FIG. 2.

Signature 8704, in these examples, provides a number of differentfunctions. For example, signature 8704 may check the integrity of acrate and its configuration items. This integrity may be performed bychecking a digital signature for the crate and its contents. In theseexamples, the signatures are located in extensible markup languagedocuments that are separate from the contents that are signed. In otherembodiments, signatures may be integral to the signed configurationitem.

Signature 8704 may sign an existing aircraft software part as well asother documents, files, and other suitable data. Unpack and inspect 8706allows a user to remove aircraft software parts and other informationfrom a crate and inspect or view those components. In unpacking a crate,unpack and inspect 8706 unzips or removes aircraft software parts fromthe crate and places them in a selected file system.

Additionally, if a packing slip is present in the crate, this packingslip also may be displayed. The inspect portion of this function may beused to allow a user to inspect the contents and signature validity ofcrates 8714 stored in file system 8712. Crate 8708 allows a user tocreate new crates and manipulate existing crates.

For example, in manipulating crates, a user may organize crates, add to,or subtract from its contents. Crates may be organized in a number ofdifferent ways, depending on the particular implementation. For example,a directory may store crates containing aircraft software parts for aparticular type of aircraft. Also, crates may be stored based on theirsource. Upload 8710 provides a function to send signed configurationitems in crates from crate tool 8700 to a library, such as library 1700in FIG. 17, in these examples.

Turning now to FIG. 88, a message flow diagram illustrating theprocessing of a crate is depicted in accordance with an advantageousembodiment. The message flow in FIG. 88 illustrates a flow of messagesused to process crates for uploading to a library.

In this example, the different components involved in processing a crateinvolve user 8800, crate tool 8802, and library 8804. The message flow,in this example, begins when a user processes or receives incoming crate8806. In this example, a user may receive incoming crate 8806 fromvarious sources. For example, incoming crate 8806 may be receivedthrough an internet connection or through some physical media, such as aflash memory or compact disc.

The user opens the crate using the crate inspection tool (operation 11).In response to this user input, crate tool 8802 displays crateinformation to the user (operation 12). The user then inspects the cratecontents and chooses to unpack the crate (operation 13). In response toreceiving this user input, crate tool 8802 validates the signatureinformation and unpacks the contents of the crate into the file system(operation 14). The signatures in incoming crate 8806 are signaturesgenerated by the source of the aircraft software part in incoming crate8806.

Thereafter, user input is generated by user 8800 to upload the unpackedaircraft software part to the library using a library upload tool(operation 15). The user enters user input to add a part to upload fromthe unpacked crate location (operation 16). The user then presses anupload to library button (operation 17).

In response to this user input, crate tool 8802 prompts user 8800 forlibrary login credentials (operation 18). In response to this prompt,user 8800 enters library credentials (operation 19). Crate tool 8802then prompts the user for a signing password to sign the aircraftsoftware part (operation 110). In response to receiving this prompt,user 8800 enters a password (operation 111). The signing password, inthese examples, is used to create the signature that is to be applied tothe various files for the aircraft software part. In response toreceiving the password from the user, crate tool 8802 applies thesignature to the different aircraft software part files (operation 112).

As part of this signing process, a new crate is created with theaircraft software part files being placed in that new crate. With thistype of implementation, the digital signatures on the aircraft softwarepart in the crate, at this stage, is different from the signatures fromincoming crate 8806. The signatures that are applied now are ones for aparticular user, such as a particular airline or maintenance facility.

After the signature has been applied, a part upload is initiated bycrate tool 8802 to library 8804 (operation 113). Library 8804 uploadsthe aircraft software part in the crate and verifies the contents(operation 114). Thereafter, an operation status is returned to cratetool 8802 from library 8804 (operation 115). Crate tool 8802 sends anevent log to library 8804 (operation 116). The event log is uploaded bylibrary 8804 (operation 117).

Next, an operation status on the upload is returned to crate tool 8802from library 8804 (operation 118). This operation status is thenpresented to user 8800 by crate tool 8802 (operation 119).

Turning now to FIG. 89, a diagram illustrating one implementation of auser interface for a crate tool is depicted in accordance with anadvantageous embodiment. In this example, user interface 8900illustrates components that may be used to implement user interface 8702in crate tool 8700 in FIG. 87. In this example, user interface 8900includes working crate list view 8902 and working crate detail view8904.

Working crate list view 8902 displays a list of different crates. Fromthis view, a user may initiate project operations 8906, working crateoperations 8908, or exit application 8910. Project operations 8906 maybe used to create a new project, open an existing project, close acurrent project, or save a current project. Working crate operations8908 allow a user to create crates, delete crates, or duplicate cratesin these examples. Exit application 8910 allows a user to exit the cratetool.

Further, from working crate list view 8902, a user may initiate open orclose working crate 8912. If a working crate is open, working cratedetail view 8904 is employed. Working crate detail view 8904 provides auser interface that may display different functions, depending on theparticular type of crate being processed.

In addition, from working crate list view 8902 and from working cratedetail view 8904, a user may access tools 8914. Tools 8914 providevarious functions, such as checking crate integrity, unpacking andinspecting crates, and checking compatibility and setting preferences.In this example, tools 8914 provide functions 8916, 8918, 8920, 8922,and 8924. Function 8916 displays information regarding the digitalsignature and the signature states of the configuration item. Examplesof signatures states are manufacturing, approval, and source.

Function 8918 unpacks a signed part and/or assets in the crate andplaces those components into the file system. Function 8920 provides foran inspection of crate contents, validates crate and componentsignatures, and manages crate files. Function 8922 allows a user tocheck the compatibility of an aircraft software part with the airplane'sonboard data load function (ODLF). Function 8924 allows a user to editvarious properties and preferences. The depicted functions are providedas illustrative examples of functions that may be provided in tools8914. Of course, other functions may be used in addition to, or in placeof, the depicted functions.

With reference now to FIG. 90, a diagram illustrating data flow ininspecting and unpacking crates is depicted in accordance with anadvantageous embodiment. The data flow illustrated in FIG. 90 may beimplemented in unpack and inspect 8706 in crate tool 8700 in FIG. 87.

In this example, two dialog boxes or views are presented, inspect andunpack view 9000 and crate inspection view 9002. Inspect and unpack view9000 is displayed to a user and allows a user to perform various actionswith respect to a crate that has been received by the crate tool. Forexample, a user may select an operation to manipulate a crate. Thisoperation may be, for example, delete or move a set of crate files.

If the user selects this operation from inspect and unpack view 9000,the selected crate files are moved or deleted (operation 9004).Thereafter, the crate list is refreshed (operation 9006), and theprocess returns to inspect and unpack view 9000.

If a user selects an operation such as removing a location, the processthen modifies the location list (operation 9008). The locationpreference is then stored (operation 9010), with the process thenreturning to operation 9006 as described above. This location preferenceis a path or direction selected by the user. In this manner, a user mayremove a location from a set of directories or a set of locations inwhich crates may be stored.

At inspect and unpack view 9000, if the user enters user input at a newlocation in this view, the user is prompted for a new location(operation 9011). Once the user enters the new location information, theprocess proceeds to operation 9008 as described above. If the userselects or decides to inspect a crate, the process moves to crateinspection view 9002. In this user interface, the user may performvarious actions with respect to a crate. For example, a user may selectto update crate information. Thereafter, crate information is read fromthe file (operation 9014). The process then updates dialog box controlswith data to display crate information to the user (operation 9016).

When crate inspection view 9002 is displayed, a user may select anotheraction, such as unpacking a crate. The selecting of this action resultsin the crate signature being validated (operation 9018). If thesignature is valid, the crate is unpacked (operation 9020). The processpresents the results of unpacking the crate along with displaying anypacking slip contents in crate inspection view 9002 (operation 9022).Thereafter, the process returns to inspect and unpack view 9000.

In operation 9018, if the signature of the crate is invalid, the processpresents the validation results (operation 9024). These results presentin crate inspection view 9002 may include an indication that thesignature problem is fatal if the validation is incorrect for a cratesignature.

In crate inspection view 9002, if the user selects to validate a crate,the process validates the crate signature (operation 9026). If the cratesignature is valid, then each configuration item signature is thenvalidated (operation 9028). In both operations 9026 and 9028, theprocess proceeds to operation 9024 to display the results of thevalidation. If a configuration item signature is not valid, then awarning is presented in contrast with a fatal problem occurring if thecrate signature is not valid. In crate inspection view 9002, if the usercloses the dialog box, the process returns to inspect and unpack view9000.

Turning now to FIG. 91, a diagram illustrating the data flow in creatinga crate is depicted in accordance with an advantageous embodiment. Theprocess illustrated in FIG. 91 may be implemented in a crate tool, suchas crate tool 8700 in FIG. 87. More specifically, the differentoperations illustrated in FIG. 91 may be implemented in crate 8708 inFIG. 87.

In this example, the process begins by opening a new or existing project(operation 9100). Thereafter, the process creates a working crate(operation 9102). In creating an initial signed configuration item, theprocess begins by receiving initial crate metadata and a configurationitem identifier (operation 9104). In these examples, a configurationitem is a single item consisting of a set of files that may be storedwithin a crate. Each configuration item has a unique identifier. Aconfiguration item may be, for example, an aircraft software part, arelated document, or some other file.

The user then navigates to the configuration item's data directory onthe file system and enters metadata for those selected files (operation9106). A directory of data files is selected because a particularconfiguration item may be comprised of more than one file. For example,an aircraft software part may include an executable file, aconfiguration file, and a dynamic link library.

Then, the process validates the metadata entries made by the user(operation 9108). In operation 9108, the process may determine whetherthe metadata entries meet a set of rules. These rules may requirecertain types of configuration items that contain certain amounts ofinformation and certain types of information. For example, with aircraftsoftware parts, a source or manufacturer of the aircraft software part,as well as an identification of the type of aircraft, may be entered asmetadata. In addition, the metadata also may identify a particularaircraft that is to receive the aircraft software part.

The process may validate the configuration item depending upon the typeof working crate (operation 9110). Next, the process receives a userpassword (operation 9112). The process then creates a digitally signedextensible markup language file for the configuration item and storesthe digitally signed extensible markup language file with theconfiguration item in the file system (operation 9114). The processproceeds to save the project (operation 9116). A user may, during any ofthese different operations, choose to halt and save the project andcontinue the project at another time.

The user then navigates to the asset's data directory on the file systemand enters metadata for those selected files (operation 9118).Thereafter, the process validates the metadata entries made by the user(operation 9120). The process receives a user password (operation 9122).The process then creates a digitally signed extensible markup languagefile for the asset and stores it on the file system (operation 9124).

Turning now to FIG. 92, a flowchart of a process for processing areceived crate is depicted in accordance with an advantageousembodiment. The process illustrated in FIG. 92 may be implemented in asoftware component, such as crate tool 8700 in FIG. 87. Morespecifically, the process may be implemented in unpack and inspect 8706in FIG. 87.

The process begins by receiving a crate (operation 9200). In thisexample, the crate may be received through various sources. For example,a physical media may be connected to or placed into the data processingsystem in which the process executes. In other embodiments, the cratemay be received through a communications link, such as a network link.

The process presents information about the crate (operation 9202). Inthis operation, the information may be presented through a graphicaluser interface. This information may include, for example, themanufacturer source of the crate, an identification of the contents inthe crate, a size of the crate, and other suitable information.Thereafter, a determination is made as to whether to unpack the crate(operation 9204). This determination may be made through receiving userinput.

If the crate is to be unpacked, the process validates signatures for thecrate (operation 9206). In these examples, the signatures may be signedusing a private key. A public key located in the crate may be used todetermine whether the manifest and file digests are valid. Thisvalidation also is used to determine whether the crate actually has beenoriginated by the source and remains unmodified or tampered with.

A determination is made as to whether the signatures for the crate arevalid (operation 9208). If the crate signature is valid, the processunpacks the crate containing the aircraft software part and stores it onthe file system (operation 9210). The configuration item signatures donot have to be valid to unpack the crate. It is up to the user whetheror not to continue unpacking the crate if one or more invalidconfiguration item signatures are detected. In these examples, if thecrate signature is valid, the aircraft software part is unpacked andstored within a file system as described in operation 9210. The processterminates thereafter.

With reference again to operation 9208, if the crate signature is notvalid, an error is returned (operation 9212), with the processterminating thereafter. With reference back to operation 9204, if theuser decides not to unpack the crate, the process also terminates.

This tool supports the work flow status and dynamics. The implementationof a user interface as discussed in FIG. 2 above allows the user tocreate, validate, and complete a crate. A crate starts with a draftstatus, and so does each component of the crate (such as the part and arelated document). As this process proceeds, the status of the crate, aswell as each component, changes from draft to in-work, and to completeas the crate is signed. The implementation also allows the user to add,delete, or modify any components of the crate. Any addition, deletion,or modification will result in a change of the current status of therelevant component and that of the crate, and thus requiresre-validation and resigning. The status is graphically indicated in bothcrate list view and crate detailed view. While providing flexibility andsupporting work flow, this functionality further ensures the integrityof completed crates.

This tool supports the dynamic release/distribution work flow status.The implementation of a user interface as discussed in FIG. 4 aboveallows the user to create, validate, and complete a crate. A cratestarts with a draft status, and so does each component of the crate(such as the part and a related document). As this process proceeds, thestatus of the crate, as well as each component, changes from draft toin-work, and to complete as the crate is signed. The implementation alsoallows the user to add, delete or modify any components of the crate.Any addition, deletion or modification may result in a change of thecurrent status of the relevant component and that of the crate, and thusrequires re-validation and resigning. The status is graphicallyindicated in both crate list view and crate detailed view. Whileproviding flexibility and supporting work flow, this functionalityfurther ensures the integrity of completed crates.

The flowcharts and block diagrams in the different depicted embodimentsmay illustrate the architecture, functionality, and operation of one ormore possible implementations of apparatus, methods, and computerprogram products. In this regard, each block in the flowchart or blockdiagrams may represent a module, segment, or portion of computer usableor readable program code, which comprises one or more executableinstructions for implementing the specified function or functions. Insome alternative implementations, the function or functions noted in theblock may occur out of the order noted in the figures. For example, insome cases, two blocks shown in succession may be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved.

Further, the different block diagrams of software components, hardwarecomponents, and data structures illustrated in this disclosure areprovided for purposes of depicting one manner in which the differentadvantageous embodiments can be implemented and are not meant to limitthe form that different embodiments may take. For example, some of theblock diagrams illustrate functional blocks that may be combined orsubdivided in software implementations. Also, the hardware andarchitecture illustrated in these examples may be varied in differentadvantageous embodiments. Also, the different examples of graphical userinterfaces are presented for purposes of illustrating one manner inwhich a user interface may be implemented. These examples also are notmeant to limit the manner in which different advantageous embodimentsmay be implemented.

The different advantageous embodiments can take the form of an entirelyhardware-based embodiment, an entirely software-based embodiment, or anembodiment containing both hardware and software elements. Someembodiments are implemented in software, which includes, but is notlimited to, forms such as, for example, firmware, resident software, andmicrocode.

Furthermore, the different embodiments can take the form of a computerprogram product accessible from a computer-usable or computer-readablemedium providing program code for use by or in connection with acomputer or any device or system that executes instructions. For thepurposes of this disclosure, a computer-usable or computer-readablemedium can generally be any tangible apparatus that can contain, store,communicate, propagate, or transport the program for use by, or inconnection with, the instruction execution system, apparatus, or device.

The computer-usable or computer-readable medium can be, for example,without limitation, an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system, or a propagation medium. Non-limitingexamples of a computer-readable medium include a semiconductor or solidstate memory, magnetic tape, a removable computer diskette, a randomaccess memory (RAM), a read-only memory (ROM), a rigid magnetic disk, afloppy magnetic disk, and an optical disk. Optical disks may includecompact disk-read only memory (CD-ROM), compact disk-read/write(CD-R/W), and DVD.

Further, a computer-usable or computer-readable medium may contain orstore a computer-readable or usable program code such that when thecomputer-readable or usable program code is executed on a computer, theexecution of this computer-readable or usable program code causes thecomputer to transmit another computer-readable or usable program codeover one or more communications links. Each communications link may beeither wired or wireless.

A data processing system suitable for storing and/or executingcomputer-readable or computer-usable program code will include one ormore processors coupled directly or indirectly to memory elementsthrough a communications fabric, such as a system bus. The memoryelements may include local memory employed during actual execution ofthe program code, bulk storage, and cache memories which providetemporary storage of at least some computer-readable or computer-usableprogram code to reduce the number of times code may be retrieved frombulk storage during execution of the code.

Input/output (or I/O) devices can be coupled to the system eitherdirectly or through intervening I/O controllers. These devices mayinclude, for example, without limitation, keyboards, touch screendisplays, and pointing devices. Different communications adapters mayalso be coupled to the system to enable the data processing system tobecome coupled to other data processing systems or remote printers orstorage devices through intervening private or public networks.Non-limiting examples are modems and network adapters and are just a fewof the currently available types of communications adapters.

The description of the different advantageous embodiments has beenpresented for purposes of illustration and description, and it is notintended to be exhaustive or limited to the embodiments in the formdisclosed. Many modifications and variations will be apparent to thoseof ordinary skill in the art. Further, different advantageousembodiments may provide different advantages as compared to otheradvantageous embodiments.

The embodiment or embodiments selected are chosen and described in orderto best explain the principles of the embodiments, the practicalapplication, and to enable others of ordinary skill in the art tounderstand the disclosure for various embodiments with variousmodifications as are suited to the particular use contemplated.

1-21. (canceled)
 22. A computer implemented method for transferringinformation with an aircraft, the computer implemented methodcomprising: establishing a connection between an onboard electronicdistribution system executing in an aircraft data processing system inthe aircraft and an on ground component; subsequent to establishing theconnection, identifying a delete command for execution by the onboardelectronic distribution system to form an identified command; sendingthe identified command to the onboard electronic distribution systemfrom the on ground component; receiving the identified command at theonboard electronic distribution system; checking a signature for theidentified command by the onboard electronic distribution system;responsive to the signature for the identified command being valid,sending a request by the onboard electronic distribution system to afile transfer system, the request comprising a request to send theidentified command to a line replaceable unit.
 23. The computerimplemented method of claim 22, further comprising: responsive toreceiving the identified command at the line replaceable unit, deletinga resource identified by the identified command by the line replaceableunit.
 24. The computer implemented method of claim 22, wherein the linereplaceable unit is selected from at least one of a flight managementsystem, an autopilot, an in flight entertainment system, acommunications system, a navigation system, a flight controller, aflight recorder, or a collision avoidance system.
 25. The computerimplemented method of claim 23, wherein the resource is selected from atleast one of an aircraft software part, a configuration or data file, ora manual.
 26. The computer implemented method of claim 23, furthercomprising: sending a request by the file transfer system to the onboardelectronic distribution system to send a status to the on groundcomponent; responsive to receiving the request at the onboard electronicdistribution system, crating the status and signing with the airplane'sprivate key by the onboard electronic distribution system to form acrate; sending the crate to the on ground component.
 27. The computerimplemented method of claim 26, wherein the status indicates whether theresource was successfully deleted by the line replaceable unit.
 28. Thecomputer implemented method of claim 22, wherein the delete commandincludes a parameter identifying a set of file names to be deleted. 29.The computer implemented method of claim 22, wherein the delete commandincludes a parameter identifying a set of part identifiers to bedeleted.
 30. The computer implemented method of claim 22, wherein thedelete command includes a parameter identifying the aircraft.
 31. Thecomputer implemented method of claim 22, wherein the delete commandincludes a parameter identifying a destination system to receive thedelete command, wherein the destination system is the line replaceableunit.
 32. A computer implemented method for receiving and storing anaircraft software part, the method comprising: receiving a crate at theonboard electronic distribution system, the crate containing an aircraftsoftware part; validating a signature for the crate and a signature forthe aircraft software part; in response to not detecting a problemduring the validating, sending a transfer request to a file transfersystem; and transferring the aircraft software part to a linereplaceable unit by the file transfer system.
 33. The computerimplemented method of claim 32, wherein validating the signature for thecrate and validating a signature for the aircraft software part includesusing a public key located in the crate.
 34. The computer implementedmethod of claim 33, wherein the signature for the crate and thesignature for the aircraft software part are signed using a private key.35. The computer implemented method of claim 32, wherein the signaturefor the aircraft software part is a signature of an airline.
 36. Thecomputer implemented method of claim 32, wherein validating thesignature for the aircraft software part comprises matching acertificate to the aircraft software part.
 37. The computer implementedmethod of claim 36, wherein validating the signature for the aircraftsoftware part is performed using cryptographic means onboard theaircraft after receipt of the crate at the aircraft.
 38. A computerimplemented method for transferring information with an aircraft, thecomputer implemented method comprising: establishing a connectionbetween an onboard electronic distribution system executing in anaircraft data processing system in the aircraft and an on groundcomponent; sending downlink data to a file transfer system by a linereplaceable unit; sending a request by the file transfer system to theonboard electronic distribution system to send the downlink data to theon ground component; responsive to the request by the file transfersystem, creating a crate for the downlink data, creating the cratecomprising signing the downlink data with the airplane's private key;and sending the crate to the on ground component.
 39. The computerimplemented method of claim 38, wherein the line replaceable line unitgenerates the downlink data unsolicited.
 40. The computer implementedmethod of claim 38, wherein the downlink data includes configurationdata.
 41. The computer implemented method of claim 40, wherein theconfiguration data is configuration data about at least one of anaircraft software part, the line replaceable unit, an airplane system,or an airplane configuration.
 42. The computer implemented method ofclaim 38, wherein the downlink data includes a report of theconfiguration of the line replaceable unit on the aircraft.
 43. Thecomputer implemented method of claim 38 further comprising: subsequentto establishing the connection, identifying a downlink command forexecution by the onboard electronic distribution system to form anidentified command; sending the identified command to the onboardelectronic distribution system from the on ground component; sending arequest by the onboard electronic distribution system to the filetransfer system, the request comprising a request to send the identifiedcommand to the line replaceable unit; and sending, by the file transfersystem, the identified command to the line replaceable unit.
 44. Thecomputer implemented method of claim 43, wherein sending downlink datato a file transfer system by a line replaceable unit comprises the linereplaceable unit processing the identified command and sending thedownlink data to the file transfer system.
 45. The computer implementedmethod of claim 38 further comprising sending a downlink command to theonboard electronic distribution system from an on ground component,wherein the downlink command was created according to input of a user,and wherein the downlink data includes data requested by the user.